This forum post has been removed
Number of replies: 5You can acquire the most recent up-to-date files from any version of Moodle directly from the repo via git.
Linux Standards Based CentOS 6 or 7 server that defines document root to be /var/www/html/
From shell, in /var/www/
git clone git://git.moodle.org/moodle.git htmlgit
cd htmlgit
git branch --track MOODLE_31_STABLE origin/MOODLE_31_STABLE
git checkout MOODLE_31_STABLE
Then ... cd ../
now in /var/www/
mv html htmlold
mv htmlgit html
html directory now contains the git acquired highest/most secure 3.1.x code.
cd html
fgrep '$release' version.php
should show:
$release = '3.1.5+ (Build: 20170324)'; // Human-friendly version name
Would think you could now copy over the moodledata directory from production server
Do sqldump of production DB. Edit sql dump search replace old url to new url
and import into dev (git acquired) DB server.
Change config.php file to reflect new locations, DB user, DB pass, DB name, etc.
Right after you do that and before you pull hte trigger on actually using, think I'd do a backup ... at least a DB dump and a tar ball of the code directory to have a fall back incase one needs to start over.
Would also clear the moodledata/sessions directory of any files as well as moodledata/cache/ contents and moodledata/localcache/ contents.
Make a separate tar ball of the cleaned up data directory for same reason ... fall back.
And you'll have a minor update 3.1.2 to 3.1.5+ to tinker with ... update will probably throw errors, etc. due to cusomizations which one would then work through.
And, if one does mangage one fix from customization, make a DB dump for the gains made to that point - again, fall back.
Hopefully, customizations are not too massive.
Good Luck!
'spirit of sharing', Ken
As a side note: you could copy the current code to /var/www/htmloriginal/
Once you have stock code in html via git one could do diff's between stock code and the customized code in htmloriginal if you know the locations of those customizations and get a real good idea as to what to look for/fix in DB.
This forum post has been removed
This forum post has been removed
Since you are attempting to move from a customized version to a
stock/standard version you need it all unless you know about the
customizations (thought you said customizations not documented ... so
some could be related to moodledata).
Data base dump and moodledata directory need to match ... ie, go togeher ... to test server. Most important directory in moodledata is filedir. It's a test run ... in the morning don't get anything new .... keep and work with what you have when you xferred it all over to dev.
Once you get the dev site up ... remember that will do an update from your 3.1.x to 3.1.5+ ... then test everything ... since you don't know what's been customized and what hasn't.
This is a test run ... not for real. Heck, the minor update might fail due to customizations. If you do get the site to 3.1.5+ not out of the woods by far. Check all the settings on dev ... nothing should refer back to production ... like URL to cron job, other/who knows. Since you don't know what's been customized have to test pretty much everything ... include backup of courses, restore of a course, reset of a course, adding a new user, etc., etc..
It ain' t gonna happen overnight, me thinks!
There really isn't any roadmap/docs written for this situation ... even if there were ... 1st step is to clone to dev ... and that's about as far as I've taken you so far.
You could be in for a bumpy ride! :\
'spriit of sharing', Ken