My apologies for the bumpy ride on this, my first ever livestream. I'll have to practice more and get better at it. During the livestream, I was unable to see any livechat messages. Even now, in spite of livechat-replay being enabled, I see no livechat. So, if you were trying to ask a question in the livechat, I wasn't ignoring you, I just wasn't able to see it. Please feel free to comment here, and I'll respond as soon as I can. Thanks to everyone who came. It meant a lot to have an audience even if I couldn't interact with you so well.
Great info! Thank you for sharing, Adam. You live, you learn!! You can edit and trim the live streams about 24 hours later. Try it so you can start at whatever point you'd like if you'd like. You can also split parts and trim them out. Let me know if you'd like to learn more.
Checkout my video on upgrading th-cam.com/video/9xds6a_aw1w/w-d-xo.html . The Process should be fairly similar regardless of whether it's on localhost or hosted elsewhere. If you need to change the URL to access it on localhost (i.e. migrating it to localhost first) then the Good migrations video will also probably help, th-cam.com/video/k0nrYdFK9uA/w-d-xo.html Also, be sure to take full backups before attempting any upgrades th-cam.com/play/PLUocP1bKm-DtdEr64NypbqLzh_MKomwac.html Happy upgrading!
It does vary depending on what your Moodle is running on. Basically you need to backup three things: the moodle code, the moodledata directory, and the SQL database. I have a playlist that goes into some depth on each of these. th-cam.com/play/PLUocP1bKm-DuLrOg_HSljgQOpM6Y589Cv.html
The main reason is because I don't know much about that topic. I mainly work with smaller scale Moodle instances where optimizing Moodle for performance yields little advantage. There is a Telegram group on Large Scale Moodle Deployment and there are Moodle docs on caching etc. but it's a bit beyond the scope of my channel. I might do a video on extremely simple clustering (2 nodes - one webserver and one SQL - not even a load balancer) but I'll probably leave the bigger scale stuff to people who are more knowledgeable about it. So, sorry as it hurts to say, but I don't know everything... at least not yet...
Hello, I upgraded my moodle from 3.11.? to 3.11.7+ by following your instructions using git pull then I used the upgrade via CLI and it works, and all my plugins/themes are still in the folder. I run this command git branch --track MOODLE_400_STABLE origin/MOODLE_400_STABLE then I git check out MOODLE_400_STABLE, but all the plugins/theme that I put manually is gone but the config.php is still there. I also checkout again the 3.11.7+ then my plugins/theme shows up. What should I do to upgrade the moodle core code only then retain my plugins and theme? Thank you
It sounds like you "added" the plugins to git. This means that git will see them as part of the repository and will "hide" the plugins when you switch to a new branch. What you need to do is reset your branch to how it is upstream and/or add the plugins to the "gitignore" file. I usually just leave them as "untracked" files which git will also ignore.
Hi WiseCat, I'm stuck with an unrelated issue which doesn't have any clear solution. I'm working for a company which wants me to migrate their Moodle from 2.4 to the latest stable version but they had modified the database tables years back without documentation, and now they don't know how to upgrade it with those table changes. What can I do to get this solved? Please help me out, thanks :)
Yikes! 2.4 with manually altered tables... That is quite a unique set of circumstances. First, and this cannot be said enough, make sure you take and keep incremental backups every step of the way as you upgrade. Being able to revert to any time along the upgrade odyssey you are embarking on will likely save you much pain later. Next, I would say you have to first diagnose and document those database table changes and check your log files for any errors that may still be happening. But actually, given the fact that those database changes were undocumented, if at all possible, I would suggest you consider backing up the courses and restoring them to a fresh install of Moodle. That way you can be sure that any changes/settings are your own and when you make them, document the changes for the next admin. Feel free to contact me if you'd like to do a call sometime wisecat.net/mod/page/view.php?id=23
I might do a video on just that soon. A lot has changed since 3.8 in terms of required SQL and PHP versions, along with a few new PHP settings that Moodle is particular about. Doing a full upgrade as a video sounds like a good idea.
Sure, it's not that tricky unless the versions of Moodle are far apart (eg. 1.9 and 4.0). As long as the PHP versions and SQL versions are compatible with both Moodle versions, you just have a second directory. Actually some people do this in lieu of a "backup" when upgrading. That would indeed make a good video on that upgrade process style. Cool idea, thanks!
According to the development docs (link below) "PHP 8.0 support is being implemented for Moodle 3.11 and later releases." So, it's only recommended to be used for development purposes and shouldn't be used on a Moodle that is used for teaching and learning. docs.moodle.org/dev/Moodle_and_PHP So you can try using it (for fun) but expect some things to not quite work right... Going forwards, 4.1 or 4.2 will probably support PHP8 (no guarantee, just my guess as of today).
After Moodle update ( 4.0+ (Build: 20220506) (2022041900.04)) I got this message: "ERROR!!! The code that you are using is OLDER than the version that made these databases!" I updated the Moodle with git/upgrade.php etc.
I tried, nothing. sudo git pull hint: Pulling without specifying how to reconcile divergent branches is hint: discouraged. You can squelch this message by running one of the following hint: commands sometime before your next pull: hint: hint: git config pull.rebase false # merge (the default strategy) hint: git config pull.rebase true # rebase hint: git config pull.ff only # fast-forward only hint: hint: You can replace "git config" with "git config --global" to set a default hint: preference for all repositories. You can also pass --rebase, --no-rebase, hint: or --ff-only on the command line to override the configured default per hint: invocation. Already up to date. sudo git status On branch MOODLE_400_STABLE Your branch is up to date with 'origin/MOODLE_400_STABLE'. nothing to commit, working tree clean 4.0+ (Build: 20220506) (2022041900.04)
@@halmizsolt5974 it looks like you may have upgraded the database before specifying the branch. Probably best to revert the SQL database to the backup from before the upgrade and retrying the upgrade.
Great stuff, man, keep going!
Thank you very much for those words of encouragement. I'm honoured!
Hey... Iam from Puerto Rico... I like your Tutorials... I learn a lot... Thanks for your contribution... :))
Thanks for your message! Glad you like the videos and hope they continue to be useful.
I think the best part is many things did not went as expected. Which is why i learnt a lot from this video. Great work.
Glad you liked it! I expect to have have many more unexpected things happen in the future (they always do) LOL.
Thanks for the video! Planning the upgrade over the summer break for our school. There will be many many backups. Keep up the good work!
Glad it was helpful! Also very happy to hear there will be "many backups"! Best of luck with your upgrade come summertime!
My apologies for the bumpy ride on this, my first ever livestream. I'll have to practice more and get better at it. During the livestream, I was unable to see any livechat messages. Even now, in spite of livechat-replay being enabled, I see no livechat.
So, if you were trying to ask a question in the livechat, I wasn't ignoring you, I just wasn't able to see it. Please feel free to comment here, and I'll respond as soon as I can.
Thanks to everyone who came. It meant a lot to have an audience even if I couldn't interact with you so well.
Great info! Thank you for sharing, Adam. You live, you learn!! You can edit and trim the live streams about 24 hours later. Try it so you can start at whatever point you'd like if you'd like. You can also split parts and trim them out. Let me know if you'd like to learn more.
'Gonna try now. I have two moodle services running on a kubernetes pod.
Sweet! Kubernetes! I've never actually tried this, but I've always wanted to...
Sir, how to upgrade manually on localhost. Please guide me. Thank you.
Checkout my video on upgrading th-cam.com/video/9xds6a_aw1w/w-d-xo.html . The Process should be fairly similar regardless of whether it's on localhost or hosted elsewhere. If you need to change the URL to access it on localhost (i.e. migrating it to localhost first) then the Good migrations video will also probably help, th-cam.com/video/k0nrYdFK9uA/w-d-xo.html
Also, be sure to take full backups before attempting any upgrades th-cam.com/play/PLUocP1bKm-DtdEr64NypbqLzh_MKomwac.html
Happy upgrading!
how and what command can i use to backup my old moodle data before i upgrade
It does vary depending on what your Moodle is running on. Basically you need to backup three things: the moodle code, the moodledata directory, and the SQL database. I have a playlist that goes into some depth on each of these.
th-cam.com/play/PLUocP1bKm-DuLrOg_HSljgQOpM6Y589Cv.html
why don't you make a video on how to optimize moodle?
The main reason is because I don't know much about that topic. I mainly work with smaller scale Moodle instances where optimizing Moodle for performance yields little advantage. There is a Telegram group on Large Scale Moodle Deployment and there are Moodle docs on caching etc. but it's a bit beyond the scope of my channel.
I might do a video on extremely simple clustering (2 nodes - one webserver and one SQL - not even a load balancer) but I'll probably leave the bigger scale stuff to people who are more knowledgeable about it.
So, sorry as it hurts to say, but I don't know everything... at least not yet...
Hello,
I upgraded my moodle from 3.11.? to 3.11.7+ by following your instructions using git pull then I used the upgrade via CLI and it works, and all my plugins/themes are still in the folder.
I run this command git branch --track MOODLE_400_STABLE origin/MOODLE_400_STABLE then I git check out MOODLE_400_STABLE, but all the plugins/theme that I put manually is gone but the config.php is still there. I also checkout again the 3.11.7+ then my plugins/theme shows up.
What should I do to upgrade the moodle core code only then retain my plugins and theme?
Thank you
It sounds like you "added" the plugins to git. This means that git will see them as part of the repository and will "hide" the plugins when you switch to a new branch. What you need to do is reset your branch to how it is upstream and/or add the plugins to the "gitignore" file. I usually just leave them as "untracked" files which git will also ignore.
Hi WiseCat, I'm stuck with an unrelated issue which doesn't have any clear solution. I'm working for a company which wants me to migrate their Moodle from 2.4 to the latest stable version but they had modified the database tables years back without documentation, and now they don't know how to upgrade it with those table changes. What can I do to get this solved? Please help me out, thanks :)
Yikes! 2.4 with manually altered tables... That is quite a unique set of circumstances. First, and this cannot be said enough, make sure you take and keep incremental backups every step of the way as you upgrade. Being able to revert to any time along the upgrade odyssey you are embarking on will likely save you much pain later. Next, I would say you have to first diagnose and document those database table changes and check your log files for any errors that may still be happening.
But actually, given the fact that those database changes were undocumented, if at all possible, I would suggest you consider backing up the courses and restoring them to a fresh install of Moodle. That way you can be sure that any changes/settings are your own and when you make them, document the changes for the next admin. Feel free to contact me if you'd like to do a call sometime wisecat.net/mod/page/view.php?id=23
how to upgrade from 3.8 to 4
I might do a video on just that soon. A lot has changed since 3.8 in terms of required SQL and PHP versions, along with a few new PHP settings that Moodle is particular about. Doing a full upgrade as a video sounds like a good idea.
Finally got around to doing this (rather long video). Hope it's not too late to help th-cam.com/video/9xds6a_aw1w/w-d-xo.htmlsi=neg_fTBCbitG2GqN
Nice tutorials , can you please make video about how to install two versions of moodle on the same server
Sure, it's not that tricky unless the versions of Moodle are far apart (eg. 1.9 and 4.0). As long as the PHP versions and SQL versions are compatible with both Moodle versions, you just have a second directory.
Actually some people do this in lieu of a "backup" when upgrading. That would indeed make a good video on that upgrade process style. Cool idea, thanks!
Cool , that's would be great 👍
I recommend you to dockerize them. In order to have no conflicts between PHP and SQL versions.
Can Moodle4.x use PHP8.x versions?
According to the development docs (link below) "PHP 8.0 support is being implemented for Moodle 3.11 and later releases."
So, it's only recommended to be used for development purposes and shouldn't be used on a Moodle that is used for teaching and learning.
docs.moodle.org/dev/Moodle_and_PHP
So you can try using it (for fun) but expect some things to not quite work right...
Going forwards, 4.1 or 4.2 will probably support PHP8 (no guarantee, just my guess as of today).
@@Wise-Cat Thank You!
After Moodle update ( 4.0+ (Build: 20220506) (2022041900.04)) I got this message: "ERROR!!! The code that you are using is OLDER than the version that made these databases!" I updated the Moodle with git/upgrade.php etc.
Try running "git pull" to make sure you have the latest code. Hope this helps.
I tried, nothing.
sudo git pull
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
sudo git status
On branch MOODLE_400_STABLE
Your branch is up to date with 'origin/MOODLE_400_STABLE'.
nothing to commit, working tree clean
4.0+ (Build: 20220506) (2022041900.04)
@@halmizsolt5974 it looks like you may have upgraded the database before specifying the branch. Probably best to revert the SQL database to the backup from before the upgrade and retrying the upgrade.
This can happen if you upgrade while on branch "master" as it can be a few commits ahead of the 400_STABLE branch.
@@Wise-Cat How can I revert the SQL database? Sorry and thank you