[#18027] - After Update to 3.8: User can create article in category via front end without having the permission for the category
- Closed
- 26 Sep 2017
- Medium
- Build: staging
- # 18027
Steps to reproduce the issue
Create a usergroup with the permissions of a publisher
Create a user in this group
Create a Category and disallow all actions for this category to the created usergroup on the permissions tab.
Login to fron tend with the created user, open front end editor and select the category without permission for the created user / usergroup
Expected result
Category should not be listed / selectable
Actual result
Category is listed and can be selected and article can be saved
System information (as much as possible)
Additional comments
Works fine with 3.7.5 after Update to 3.8 issues appears
Votes
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | ACL com_content com_users |
| Status | New | ⇒ | Confirmed |
Status at Issue Tracker now "Confirmed".
Anybody solved the problem?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18027.
Sorry I'm new here. This means that you know the problem but no one knows what to do about it. I have to wait for version 8.1 and then maybe it will be fine?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18027.
It means no Developer had time or willing to create a Pull Request.
More about reporting Bugs and Pull Request read please in the Documentation.
This issue effects the specifically the top level categories
and also only the category themselves only, their descendants are excluded
please see the PR i made for more details
zero-24
- | Status | Confirmed | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-09-26 21:10:46 |
| Closed_By | ⇒ | zero-24 |
sorry but where is the PR by ggppdk ?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18027.
ok, I found it: https://issues.joomla.org/tracker/joomla-cms/18131
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18027.
I can confirm the problem, also in backend.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18027.