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?
We are trying to upgrade from 3.5.1 to 3.5.17 (our DEV server) and had similar issues. I ended up updating the plugin first (as I am updating from 3.5 to 3.5). When updating it said there is a higher version already installed. So I added the sub folder of the plugin from the server to the zip file of the plugin and manually installed it. I don't think this was the proper way to do it but it accepted it.
How were you able to 'add' the subfolder 'hotpot' from the server to the zip file? The contents of the zip file already has a 'hotpot' folder in it? And the 'hotpot' folder from the server would be the old version, right? And the zip file has the 'newer' version?
The plugin was customlabel. The "other" mod was keypoints it was in the customlabel/type/keypoints folder of the zip. We used 7zip and opened the zip file. Just removed the subfolder that was considered another plugin and added it back from the server. Not the whole plugin.
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.