[#7848] - Custom ACL fine-tuning through plugins
- Closed
- 14 Mar 2016
- Medium
- Build: staging
- # 7848
- Diff
- themaze75:menu-event
- Failure The Travis CI build failed Details
User tests: Successful: Unsuccessful:
This is a series of dispatches we've been using since Joomla 2.5.
Essentially, we try to provide Web site managers with the best streamlined UX possible, which means removing any features from the backend that is not used to manage the Web site's content.
This series of dispatchers allows our plugin to hide certain components and modules from the backend using our own logic, going beyond what the standard Joomla ACL allows to do.
For example: allowing only certain types of modules to be created, preventing the modification of certain modules, hiding parts from the UI that is out of reach of the ACL (ex: blocking user notes and user mail)
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Labels |
Added:
?
|
||
zero-24
- | Category | ⇒ | ACL Feature Request Plugins |
It would add new events to the core to allow the existence of such plugins.
The other (arguably better) route would be to enhance the ACL model to allow even finer control over what is available to certain access levels. Granting acces to certain views of components, grant /block access on certain module instances... that would be a much larger scope feature.
This is a change that is very specific to you. If we would implement something like this, we would have to implement it in A LOT more places than just here. At the same time, I think the plugin system is the wrong way to go for modifying queries all over the place. So I don't think that we should accept this PR.
Besides that you have codestyle errors and I doubt that this would work with PHP7 correctly.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-03-14 14:24:11 |
| Closed_By | ⇒ | themaze75 |
If I'm not wrong you are triggering non-core event
So what's the point of this pr without the plugins