Core plugins review for Moodle 4.0: Difference between revisions
David Mudrak (talk | contribs) m (Mudrd8mz moved page Core plugins review to Core plugins review for Moodle 4.0: Rename to make the target version clear and have the page put into the time context) |
David Mudrak (talk | contribs) |
||
| Line 29: | Line 29: | ||
* Jabber notification plugin (message_jabber) | * Jabber notification plugin (message_jabber) | ||
* Assignment 2.2 module (mod_assignment) | * Assignment 2.2 module (mod_assignment) | ||
Note the plugins can be added to the Plugins directory only once the target version 4.0 is registered there, which happens on beta release. | |||
==Plugins we are thinking about removing from core and adding to the plugins directory== | ==Plugins we are thinking about removing from core and adding to the plugins directory== | ||
Revision as of 07:52, 27 September 2021
| Core plugins review | |
|---|---|
| Project state | In progress |
| Tracker issue | MDL-72046 (epic) |
| Discussion | Moodle core plugins review |
| Assignee | Sara Arjona |
Introduction
This project is about reviewing the plugins in core Moodle LMS with the aim of removing any which are no longer or hardly used, and if appropriate, adding them to the Moodle plugins directory.
Plugins to be deleted from core
The following plugins will be deleted from core but not put in the plugins directory because the technology is discontinued.
- WebCT question import/export format (qformat_webct)
- Examview question import format (qformat_examview)
- Flash animation media player (media_swf)
- VideoJS Flash plugin
- Picasa repository (repository_picasa)
- Picasa portfolio (portfolio_picasa)
- Microsoft OneDrive (legacy) (repository_skydrive)
Plugins to be removed from core and added to the plugins directory
Plugins which are removed from core and added to the plugins directory will initially be listed with Moodle HQ as maintainer while we seek new maintainers via the Plugins adoption programme.
- Word censorship filter (filter_censor)
- Health center admin tool (tool_health)
- Jabber notification plugin (message_jabber)
- Assignment 2.2 module (mod_assignment)
Note the plugins can be added to the Plugins directory only once the target version 4.0 is registered there, which happens on beta release.
Plugins we are thinking about removing from core and adding to the plugins directory
We still need to decide which of the following plugins should be removed from core and added to the plugins directory. Please let us know your thoughts by posting in the discussion on moodle.org Moodle core plugins review. We will collate all your feedback and review what to do with each plugin.
- Quiz results block (block_quiz_results)
- Flickr block (block_tag_flickr)
- Examview question import/export format (qformat_examview)
- Algebra notation filter (filter_algebra)
- HTML tidy filter (filter_tidy)
- Box repository (repository_boxnet)
- Legacy course files repository (repository_coursefiles)
- Equella repository (repository_equella)
- Flickr repository (repository_flickr)
- Flickr public repository (repository_flickr_public)
- Merlot.org repository (repository_merlot)
- URL downloader repository (repository_url)
- Box portfolio (portfolio_boxnet)
- Flickr portfolio (portfolio_flickr)
- Mahara ePortfolio (portfolio_mahara)
- Survey activity (mod_survey)
How will these plugins be removed from core?
- The plugin folder (for instance, question/format/webct/ for qformat_webct), will be completely removed from Moodle core. IMPORTANT: if you want to keep any of the plugins removed from core in your Moodle site, you will need to download and copy the plugin folder to the right place BEFORE running the upgrading process.
- Each plugin will be removed from the standard_plugins_list() method and added to the is_deleted_standard_plugin() method (both placed in lib/classes/plugin_manager.php).
- The upgrading steps will be added to lib/db/upgrade.php, to remove specific tables and settings (when it applies).
The plugins data will be removed only if the plugins files are not present anymore in the code. So, if a site wants to keep any of the plugins removed from core, they should download and copy the plugin folder to the right place (as they use to do with third-party plugins) BEFORE running the upgrading process.
