Dear all -
I have just upgraded a production server from 2.4 to Moodle 2.5+ (Build: 20130621). Site administration link has become non-responsive, just like many others (see attached screenshot: clickable links are blue, non-clickable - grey).
Naturally, no work can be done.
Reinstallation of the same script did not help.
Anyone seen this before? Any ideas? This is pretty urgent, as the next exam is tomorrow.
Is Site Administration a Block?
Is Users a Block?
Went over #13. tried purging the cache for the site and for the theme. No change.
Nothing else in your sleeve?
OK, went through the entire thread. It's barking at the wrong tree: it's about specific courses and blocks. In my case, I just cannot proceed past the home page: very few menu links work. Neither Users and Site Administration can be clicked to display submenus.
Clearing site cache and theme cache did not resolve the issue.
I cannot even enable debugging.
And 80 different groups of students and their coordinators yelling at the secretaries that they cannot use the site.
Please suggest a solution! Even a workaround would do.
That was mean... I was hoping for a point-and-click solution, not a dirty coding one.
Now I need to roll up my pants and jump into the weeds...
OK, will do and report what I manage to harvest.
If you're not able to find an immediate solution, you may be better off installing 2.4 in parallel and restoring your site into that install, just to get you up and running again...and get the secretaries off your back.
I have given it some thought. I might even try to install another 2.5 back to back, check it out to see it works ok; if it does I can try to manually migrate the user data and the content there.
If it does not I may do the same with a 2.4.
In any case, it will need to be done over the weekend.
But first I will try to enable debugging and see (and share) what there is to see.
Reporting the results of the first test:
- installed a clean 2.5 to a parallel location on the same server
- everything works fine.
Bottom line: something is screwed in the upgraded 2.4 => 2.5 installation.
I wonder if I should try to run a Repair DB in the cPanel.
You could. If that doesn't work, restore the backup you made prior to upgrade into the working 2.5 installation.