Fixed
Details
Details
Priority
Affects versions
Components
Labels
Assignee
David Mudrak
David MudrakReporter
David Mudrak
David MudrakPeer reviewer
Petr Skoda
Petr SkodaIntegrator
Dan Poltawski
Dan PoltawskiFix versions
Tester
Simey Lameze
Simey LamezeParticipants
Dan Poltawski
David Mudrak
Marina Glancy
noreply
Petr Skoda
Simey Lameze
Pull from Repository
Pull Main Branch
MDL-48156-master-pluginisenabled
Clockify
Clockify
Created 10 November 2014 at 17:45
Updated 4 August 2022 at 09:57
Resolved 12 November 2014 at 20:28
In the https://moodle.atlassian.net/browse/MDL-46207#icft=MDL-46207, we introduced a check for the plugin enabled/disabled status. Since 2.8, we do not execute tasks for disabled plugins unless the task explicitly overrides this behaviour via `get_run_if_component_disabled()` method.
However, the world is not black and white. Many of our plugin types (most actually) do not have support for enabling/disabling individual plugins. For these, the plugininfo's `is_enabled()` returns null (as documented in that method's phpDoc).
The trouble is that we do not execute tasks for these plugins too - we consider them all as disabled. Which is IMHO wrong. We should explicitly check for really disabled plugins.