Hi there,
I'm upgrading a Moodle site (in DEV), from 3.3.9 to 3.6 to 3.9.1. I've just completed the Moodle 3.6 upgrade, but I am stuck at the plugins screen as Moodle tries to revert the HotPot plugins to an old version for some reason. I can't seem to get away from this screen - it redirects back here. Upgrading the database results in the cannotdowngrade error code. We are actively using this plugin, so deleting then installing the plugin isn't ideal, as it will also delete all instances of the plugin across the site. How do I fix this?
Moodle stuck trying to revert the HotPot module as part of upgrade
에 Matthew Willis 씀
Number of replies: 4
In reply to Matthew Willis
This forum post has been removed
The content of this forum post has been removed and can no longer be accessed.
In reply to Deleted user
Re: Moodle stuck trying to revert the HotPot module as part of upgrade
에 Cris Asuncion 씀
In reply to Cris Asuncion
This forum post has been removed
The content of this forum post has been removed and can no longer be accessed.
In reply to Matthew Willis
Re: Moodle stuck trying to revert the HotPot module as part of upgrade
에 Cris Asuncion 씀
Hi Matt,
After some further analysis, I noticed that the 'main' Hotpot plugin has a newer version in the zip file, but 'sub-plugins' or subfolders that seem to be further plugins (above) have their versions old (in their version.php files) that's why update fails. So in order to 'force' the system to install them along with the main Hotpot zip file, I just manually modified their version.php information and replaced them with anything higher than currently installed version - i.e. 2014061824.
Regards,
Cris
After some further analysis, I noticed that the 'main' Hotpot plugin has a newer version in the zip file, but 'sub-plugins' or subfolders that seem to be further plugins (above) have their versions old (in their version.php files) that's why update fails. So in order to 'force' the system to install them along with the main Hotpot zip file, I just manually modified their version.php information and replaced them with anything higher than currently installed version - i.e. 2014061824.
Regards,
Cris