Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server.Do NOT copy new files over the old files. Move your old Moodle software program files to another location.
You can download the latest release from Moodle downloads. Then you should wait for any currently running cron processes to complete before proceeding. If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.īefore you begin upgrading your site, you should put it into maintenance mode to stop any non-admin users from logging in. The upgrade of the plugin will then happen as part of the Moodle upgrade process. In the next step, you will copy it to the appropriate location in your Moodle code (see Installing plugins). If you are updating plugins manually, it is a good moment now to check in the Moodle Plugins directory whether there is a 3.11 version available for any plugins (including themes) that you have previously installed on your site. Just make sure you check for available updates (via the button for it) at the Plugins check screen.
LINE 6 POD FARM 2.5.7 UPGRADE CRACK UPDATE
If you have Automatic updates deployment enabled, you will be able to update installed plugins automatically during the upgrade. See Site backup for more specific information.
If upgrading from earlier versions, you must upgrade to 3.6 as a first step. You can only upgrade to Moodle 3.11 from Moodle 3.6 or later.See the release notes in the dev docs for both server and client software requirements. 9.4 Moodle 3.6, 3.7, 3.8, 3.9 and 3.10 improvementsīefore upgrading, check that your server meets all requirements for 3.11 in Site administration > Server > Environment.9.1 Activity dates and completion conditions can be shown on the course page.9 Possible issues that may affect you in Moodle 3.11.7.1 Fatal error: Maximum execution time of 30 seconds exceeded.