Moodle™ plugin rescue
Is one plugin blocking your Moodle™ upgrade?
A single plugin that breaks or is no longer maintained can hold up your entire upgrade. We quickly find out what exactly is wrong, whether it can be fixed and what it takes to move on. Wherever your Moodle runs: you do not need to be hosted with us.
Sound familiar?
- A plugin throws errors during or after an upgrade.
- The author has disappeared or no longer ships updates.
- The plugin does not support your target version yet.
- You do not know whether it can be fixed or whether you need an alternative.
What you get
- A clear picture of what exactly is wrong.
- Whether it can be fixed, and if so: how much work it is.
- Concrete next steps: repair, rebuild, replace or drop it.
- Honest advice, even if the conclusion is that it is not worth it.
Why plugins break during an upgrade
With every major version Moodle changes under the hood: hooks, APIs and database structures shift. A plugin that does not keep pace breaks. The most common causes:
- The author stopped and never updated the plugin for a newer Moodle.
- The plugin relies on code or APIs that Moodle has removed.
- There are changes in core or the theme that break during the upgrade.
- The plugin does not meet the PHP or database requirements of the new version.
Tell us what is going on
The more we know up front, the more precisely we can look. Only name and email are required.
Prefer to talk through your situation first? Book a call.
Is more than one plugin overdue? See how we take over Moodle management →