Moodle 3.2 admin issue

Re: Moodle 3.2 admin issue

by Kevin Schiller -
Number of replies: 2

Hi there,

We are transferring courses from our current LMS site to our test environment LMS for testing.

As we were trying to do a Moodle 3.5 update on our test enviroment. Due to shared server on DreamHost, that is only capable of running antipope file format in mysql and not baracuda, and we cant perform the moodle upgrade operation. So, we restored our LMS to Moodle 3.2 on the shared server.
Now, after reverting to moodle 3.2 some of the tabs in site administration page are not accessible. For Example: site administration > Users.
We cant seem to fix this issue.

Any help would be greatly appreciated!



In reply to Kevin Schiller

Re: Moodle 3.2 admin issue

by Ken Task -
Picture of Particularly helpful Moodlers

Trying to understand ... you attempted an upgrade from 3.2 to a higher 3.x only to discover hosting wouldn't allow changing DB server config.   Right so far?

You did begin by backing up the DB (sql dump) and a backup of code directory right?

So in reverting back, one would have to restored the original 3.2.x DB and the original 3.2.x code directory and that's what you put back.  Is that right?

Through this attempt the same moodledata directory was being used ... soooo ... if above is accurate, then suggest manually removing contents of moodledata/cache/ moodledata/localcache/ moodledata/sessions/ then, for good measure, restart the apache service.   On your work station being used ... clear cache/cookies etc. related to the site.

Then attempt accessing the site to see if one can get the old site with admin menus.

'spirit of sharing', Ken


In reply to Kevin Schiller

Re: Moodle 3.2 admin issue

by Howard Miller -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

There's nothing about barracuda/antelope that stops you upgrading. It's a recommendation, not a requirement.