 Okay, let's upgrade your Moodle. So you're logged in to your current Moodle as an administrator. By the front page, you're going to go to Server, Maintenance Mode, Enable Maintenance Mode. There's optional messages that you can leave there for your non-admin's who won't be able to log into the site during maintenance mode. Ideally, you've given everybody advanced notice and you've probably chosen a period of low activity to take your site offline. So it's now in maintenance mode. We're in a position to back up a few things before we proceed with the upgrade. So you're probably using, depending how you're hosting your Moodle on your servers or somebody else's, you may be using Control Panel like C Panel or Plesk. When you've logged into your set account, you should be able to get to your databases. So PHP My Admin's a fairly typical way to access your MySQL. And you'll want to grab a copy of your database. That'll be the first thing in SQL format. So save that on your computer somewhere away from the server that's hosting your Moodle. So that's the first thing you do. That will be a .sql file. Back over to your Control Panel. You'll also want to grab copies of the Moodle software and the Moodle data directory that contains all of your courses and associated data. You config .php file, which is contained within the Moodle software directory. And certainly any third party plugins and custom themes and the like that would be overwritten by an upgrade. Okay, so you'll want to have those things, put them aside, and you're certainly going to need some of them to be able to carry across your upgrades successfully. And certainly you'll need all of those things in the event that you've got to roll back to your currently old Moodle version. All right, so all is good there. Let's presume we've downloaded and we've got our backups safely put aside. Over at Moodle.org, you've got to the Downloads section and naturally you choose your preferred flavor of Moodle. You're going to select a current stable release, most likely. There's older stable builds. It's indicated by the version numbers. And then you've got the latest upcoming releases. These aren't stable or necessarily production ready. They're more for developers and people looking to test Moodle in a non-production environment. So we've done this already, but we've downloaded the latest stable current release of the Moodle software to our computer and then uploaded it to the public HTML folder, or the web root, or the HT docs, depending on what you call that area, and your Moodle server. So it's sitting there as a zip file at the moment. What you'll want to do now before you proceed is rename your current Moodle folder in the public HTML directory. Out of something else. Okay, so we've renamed that folder. Let's extract the latest stable Moodle release that we've just downloaded, and then the FTP to this location. So that's being extracted as we speak. Okay, and again, we'll name this new extracted folder Simply Moodle. We'll just navigate to that folder. At this point in time, it won't have a config file. This is the new software. We'll want to upload the config file from the old Moodle instance with the database settings, the user names, password, web root, data directory, and the like as part of that configuration. So those things should remain unchanged. So back over at our Moodle instance, there will be a case of running the notifications page or your Moodle address forward slash admin, and we should be in a position to move forward with the upgrade. Okay, so we're running through that now. You can check the status of your environmental settings there. If there's any red flags, you won't be able to proceed. These are things that certainly relate to you, you know, your MySQL database, your PHP extensions and libraries, settings and the like. Again, we can see potentially some third-party plugins that were left behind. Okay. They needed to be copied across into the new Moodle data directory. Activities and blocks. So bear these things in mind. You may in fact not want to bring them across, but if you do, be mindful not to leave them behind. So at this stage, as your Moodle's upgrading, you know, database tables and the like are being updated. Hopefully it's all green lights. It should be success. Continue as we just move forward. There's some new settings, configuration settings that need to be set with the upgrade. We could certainly leave the defaults if need be and revisit these at a later stage. So there you have it. We have upgraded our Moodle to the latest stable release.