[#15524] - [com_cache] advanced permissions ACL reports
- Fixed in Code Base
- 18 Nov 2017
- Medium
- Build: staging
- # 15524
- Diff
- alikon:patch-89
- Success continuous-integration/drone/pr the build was successful Details
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success continuous-integration/appveyor/pr AppVeyor build succeeded Details
- Error continuous-integration/jenkins/pr-merge This commit cannot be built Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #14959 .
Summary of Changes
moved actions from config.xml to access.xml
Testing Instructions
Users->Manage->Advanced Permissions Report
Expected result
Actual result
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_cache |
can you list the other's please
Just work through the select list - it is almost everything that is listed there that is NOT a traditional component like content eg Ajax, Content history, categrories etc
yes i see now ....
it does look like you correctly found the reason - I had failed in that search
Works fine for the 2 below views, however only when the filtering is on for Cache
administrator/index.php?option=com_users&view=debuguser&user_id=851
administrator/index.php?option=com_users&view=debuggroup&group_id=10
Without filtering we have the previous display, is it the expected behavior?
i'm not sure what should be the correct behavior without filtering, cause you may have different item's listed,
so the action that can be correct for an item (for example an article) cannot be correct for another one (for example com_cache)
| Labels |
Added:
?
|
||
@alikon Can you elaborate on what the issue is?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15524.
this pr fix the list of permissions showed when the com_cache is selected (i.e ony the permission related to com_cache (core.admin,core.manage))
but if you don't select a component, the list of permission showed are general permissions
in addition as @brianteeman #15524 (comment) pointed out, we stil need to manage componen'ts like com_ajax, com_contenthistory, etc.
imo the latter should be a better way
I have tested this item
Tested on 3.8RC1, this is fixing the com_cache when filtering is on.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15524.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15524.
| Status | Pending | ⇒ | Ready to Commit |
RTC after two successful tests.
mbabker
- | Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-11-18 15:57:30 |
| Closed_By | ⇒ | mbabker | |
| Labels |
Added:
?
|
||
I have tested this item✅ successfully on f52c85f
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/15524.