This issue is created to set the idea of adding the functionality to ignore Moodle plugins from MDL-38109 in motion. MDL-38109 has quite a long discussion on why this functionality is needed or why it could be useful for Moodle partners. There was no feedback or ideas given on what would be an acceptable solution for the ignore plugins idea to make it into Moodle.
Feedback or any ideas for this would be greatly appreciated before any actual development starts.

Some of the ideas and concerns raised in MDL-38109 and new ideas here include:

• have config.php accept a new setting $CFG->ignoreplugins that will be a CSV list of plugins prefixed with frankenstyle format

• adding a new boolean configuration setting such as "Notify user of hidden plugins" indicating whether the user will be notified that any plugins were ignored

• If we allow the user to be notified of ignored plugins then how should that be done?

– The first point of notification is the "Plugin check" page that is shown when a plugin needs updating. That plugin page has a table with the field "Status". If a plugin is ignored it might make sense to label that plugin as "Ignored" under the "Status" field.

– The second place where a user can view plugins is the "Plugins overview" page. The "Plugins overview" table has a field called "Availability". If a plugin is ignored it might make sense to label that plugin as "Ignored" under the "Availability" field.

• Once a plugin has been enabled (as in there is an instance of it) then we may not want to ignore it. We may only what to ignore plugins with zero instances.

• Should we allow ignoring of Moodle core plugins or just custom (non-Moodle) plugins?

• Dependency issues when trying to ignore plugins