[#32117] - [3.9.24] [4.0.0-beta6] com_content ACL selected catid is not recognized
- Closed
- 20 Feb 2021
- Medium
- Build: 3.9.24
- # 32117
Steps to reproduce the issue
I have a user group that is allowed to create, edit and publish articles in the frontend for a specified category.
User group is below "Registered", global permission are "inherited". Special permissions are "allowed" in the category.
Actual result:
If a user of this group wants to create a new article, then the fields for publishing are not available.
If this user wants to edit an existing article, then the fields for publishing are available and can change them.
Expected result:
For a new post, the fields for publishing should also be available if this is set in the category permissions.
System information (as much as possible)
Joomla 3.9.24
PHP 7.4
Additional comments
My investigation has shown that the selected category is not recognized and therefore not its permissions.
My instructions for the authorization https://it-conserv.de/blog/berechtigungen-fuer-ein-verein.html
Votes
joomla-cms-bot
- 
In version 4.0.0-beta6 there is the same problem.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32117.
Create a new article in version 4.0.0-beta6 with the same settings and without enabled workflow.
The state field is showing, but is disabled. After save is the state of this article not published.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32117.
| Title |
|
||||||
version 4.0.0 beta6 extended
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32117.
We can confirm this issue as well. In addition to the already pointed out topics, our users within the special journalists-group are not even able to go into any created article in the backend.
As a superuser, I'm able to do all the stuff I need to do within an article, but with any other permission, I'm not even able to edit the article (see second screenshot below).
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32117.
@joomdonation Would the fix for J3 be the same? If so, it might be better to fix it in staging, which will later be merged up to 3.10-dev and 4.0-dev anyway. Or is the fix a kind of B/C break so we can't do it in J3?
@richard67 The PR contains some improvement to our existing code (which I don't want to make change to to staging right now)
I will see if I can make a fix for staging with minimum change needed. If Yes, I will submit a separate PR for staging.
I understand, thanks for feedback.
As this issue here is for J3, too, I suggest we leave it open until it's clear what we will do for J3.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-02-20 13:33:57 |
| Closed_By | ⇒ | richard67 |
I can confirm this issue.
See also #17812
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32117.