Upgrade failure

Upgrade failure

by M. V.W. -
Number of replies: 2

I am trying to upgrade from 2.23+ to the current 2.5+.

I wanted to test it out on a copy first (not production site).

I created a new MySQL database into which I imported the production DB.

I created a new moodledata folder in root, but in a new location, and put in there all contents from production moodledata folder.

And in a new subdirectory, I copied all files from production site's folder. But customized the config.php to the new DB & moodledata location and moodle files location.

I tested it out - it works perfectly - an exact copy.

I then removed all files and folders from the new subdirectory.  I then copied there the 2.5+ download's files and folders.

I went back to this copy site, and it triggered the upgrade process.  It passed all requirement tests.  It then scanned plugins and found a few missing.  I manually copied 1 activity and 3 blocks from the production site.  I reloaded this page, and it showed everything ready for upgrade.

I then did the upgrade process, and no errors were triggered.  Everything seems perfect.

I purged all caches manually.

Now I'm in 2.5+.  Everything seems fine... until... I go to notifications and get a blank screen.  I try some of the other system admin settings - such as unit tests, or other tests.  Each produces a blank screen.  I figure I'll debug. But when I go to debugging -- I get a blank screen.

I try to edit a course by adding a resource - a page - and the tinyMCE editor only shows two icons - a greyed out "break link" icon and an insert media icon - but nothing else - not even bold or italics.

Something definitely is broken -- but without being able even to trigger DEBUG features, I'm stumped!

Help!

Average of ratings: -
In reply to M. V.W.

Re: Upgrade failure

by Helen Foster -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

Hi,

Please see the documentation Debugging for details of how to enable debugging if you can't get to the admin page.