Log as super user in back-end.
Create a user as administrator in back-end.
Logout
Log in back-end with this new user
The new user should be asked to consent to the Privacy policy
It does not
Labels |
Added:
J3 Issue
?
|
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.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-10-18 05:16:38 |
Closed_By | ⇒ | infograf768 |
Closing as this is intended behavior.
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!
Note: It does work OK in front-end