Extendibility of Privacy Capabilities #36727
matteo-galletti
started this conversation in
Ideas
Replies: 1 comment
-
Moving this to discussions |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
The capabilities listed by com_privacy component can be extended only through a plugin that belongs to one of the pre-selected groups. What if I need to mention the cookies used by a component without the usage of a plugin?
Describe the solution you'd like
I would like to propose a new technique to allow the extendibility of the capabilities list simply by relying on the helper file (and related class) that a component or a module might have already declared to support the
prepareUpdate
method, invoked byUpdateModel::preparePreUpdate()
.In case of a component, the resulting file should be already built as follows:
My request aims to introduce a new static method to allow the components and the modules to return a list of points to be displayed within the Privacy: Extension Capabilities page. So, if we take a component named com_foo as example, the class previously described should become:
At this point the
CapabilitiesModel::getCapabilities()
method should load the list of all the installed components and modules and scan them one by one to look for the helper file:My entire request is based on a piece of code already used by the
getCapabilities()
method. Here it is:Why com_privacy should be able to "cheat" and com_foo not?
Additional context
All the administrator modules should be completely ignored, since their effect cannot interfere with the front-end user experience.
Should the system ignore the extensions that have been disabled? In case the answer is yes, then the system should fetch a list of installed components and site modules from the
#__extensions
database table. Alternatively it would be enough a direct foreach to the targeted folders. Something like:Beta Was this translation helpful? Give feedback.
All reactions