Closed aschempp closed 1 year ago
What I don't get conceptually is: How would you decide if a plugin is disabled or not? You do not have access to the container for instance. So file system access on every request? Because otherwise you could as well check it once in getBundles()
(and return []
in case).
What I don't get conceptually is: How would you decide if a plugin is disabled or not? You do not have access to the container for instance. So file system access on every request? Because otherwise you could as well check it once in
getBundles()
(and return[]
in case).
That's a question we can't really answer just yet. Our idea was that one could e.g. do a license check, but yes it obviously needs to be something very low-work. Maybe we should discuss the idea again.
As discussed on the Contao Call we don't want to add this feature. It potentially causes issues if a plugin is disabled at runtime, and it still is possible to bypass all existing methods in a plugin if really necessary.
This allows plugins to be disabled dynamically, e.g. for validation a license.
It is intentionally called "DisabledPlugin" because