J3 Issue ?
avatar infograf768
infograf768
16 Oct 2018

Steps to reproduce the issue

Log as super user in back-end.
Create a user as administrator in back-end.
Logout
Log in back-end with this new user

Expected result

The new user should be asked to consent to the Privacy policy

Actual result

It does not

Votes

# of Users Experiencing Issue
1/1
Average Importance Score
5.00

avatar infograf768 infograf768 - open - 16 Oct 2018
avatar joomla-cms-bot joomla-cms-bot - change - 16 Oct 2018
Labels Added: J3 Issue ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 16 Oct 2018
avatar infograf768
infograf768 - comment - 16 Oct 2018

Note: It does work OK in front-end

avatar mbabker
mbabker - comment - 17 Oct 2018

This was the system design. If someone wants to propose an option to require it for the backend I personally wouldn't be opposed to it, but I don't think it needs to be a hard requirement for the backend the same way it is frontend.

avatar infograf768 infograf768 - change - 18 Oct 2018
Status New Closed
Closed_Date 0000-00-00 00:00:00 2018-10-18 05:16:38
Closed_By infograf768
avatar infograf768
infograf768 - comment - 18 Oct 2018

Closing as this is intended behavior.

avatar infograf768 infograf768 - close - 18 Oct 2018
avatar mc-cm
mc-cm - comment - 21 Nov 2018

Seems I'm the only one who actually hase a requirement for the privacy consent features in backend. I have many users whom I give backend access (actually all publishers) to the sites. We do a backend only strategy, and therefor I'd like to see the consent privacy features of J3.9 applied also to the backend. Thanks!


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22659.

Add a Comment

Login with GitHub to post a comment