I understand the Hot Potatoes plugin is yet to be updated for Moodle 2.0. Remove any non-core plugins and you may have more success. If you are trying to update a Moodle 1.9.x to Moodle 2.0, then you may have considerably more success with a completely fresh install.
Actually, I think Gordon has just released Hotpot for M2, but there are some issues not yet clear (both as to HotPot and other non-core mods on upgrade to M2.)
While it is apparent that upgrading to Moodle 2 fails when non-core mods are installed (is there something in the upgrade docs that addresses this yet?) users are advised to "remove" non-core mods, but users are not told specifically what steps to take to accomplish this.... Do they have to just turn off the mods in the admin GUI? Do they have to delete the mods from the admin GUI?, do they also have to physically remove the mods from the file system?
While I had posted some time ago about issues with M2 previews crashing on mods, that issue has been now closed without any explanation as to how M2 now avoids the problem, and as many people have complained that this is still apparently the behavior they see in M2, I'd have to argue that anyone with a Moodle 1.9 has a significant chance of losing everything by upgrading to Moodle 2 without have a detailed picture of why M2 is crashing on upgrade and a clear and concise recitation of the actual steps one must take to possibly avoid any disaster.....
Hi all,
I don't know about "mod_imscp", but I do know that the HotPot module for Moodle 2.0 is now up and running (yay!) It will update all your Moodle 1.9 HotPots ready for use in Moodle 2.0.
regards
Gordon
However, what remains to be clarified for users is what procedures they need to follow if they wish to upgrade from a Moodle 1.9.x (with hotpot module installed), to Moodle 2. This is no triviality as we have seen so much grief over upgrading to M2 over non-core modules.
I tried ignoring the messages but all that happened in my case was that it kept telling me that I had non-standard mods and never progressed beyond that page. That is what led me to posting a message in this forum and subsequently I reverted to 1.9 so I am unable to recreate the prob
I am not 100% sure (because as I mentioned I just used an FTP program to synchronize the two sites) but why would old 1.9 code interfere with 2.0 code? Surely that is a problem in itself.
We have decided to put 1.9.1 on our new server. Tried 2.0 but a lot of issues yet and no support yet even some of the basic modules. No good way at this point to move 1.9 data to 2.0. I don't have full time IT support and we can't have a flakey install as these are K12 student credit courses.
I understand that BUT (as a former programmer) if I replace all of the modules that were there with new modules wouldn't that also change all of the low-level APIs. How could the old APIs get called if their 2.0 versions are there. The 2.0 APIs should override any 1.9 versions ... or is that not true?
I know that this is an old thread ... but previously I reported that I completely reinstalled 1.9 so I was just making an comment.
mmm I would suggest that it is not just a matter of code or APIs but the table and field structures as well. It does not matter that the newer database overwrites the older, but the steps to make it work when tables have been dropped, fields altered, Indexes changed, just so many things different, that you may never have a situation where a Moodle 1.9.x can be updated, you have to create a new install. You cannot mix and match - simple as that. One example I can think of is that we used CP/M-DOS then MS-DOS v2 and about v3 or 4 Windows 3.1 came along. Eventually DOS went up to v6, then Windows 95 arrived and so on and now Windows 7 is the probable equivalent of about DOS v11. Each step was a logical, almost, progression from the previous yet each builds on the previous. Not so with Moodle 1.9.x and v2.0. This is stepping from DOS v1 directly to Windows 7, some common elements but huge differences - too many for them to work together.
