Before proceeding to update the database schema, make a full backup of the wiki, including both the database and the files: While the upgrade scripts are well-maintained and robust, things could still go awry. Use runJobs.php to run all pending jobs and clear the queue before performing the upgrade.īack up existing files and the database Full instructions: Manual:Backing up a wiki It's strongly recommended to run those pending jobs before upgrading the wiki, to avoid them failing in case the parameter specification of those jobs change on the new version. Those jobs are stored in database and contain parameters with information about actions it should perform. You should also read the instructions in the UPGRADE file.įor performance reasons, some actions in the database are delayed, and are managed by the job queue. Now's the time to open it up and find out what's been changed in this release. Within the distribution tarball, or within the files checked out/exported from Git, there are a number of files with capitalized filenames, one of which contains the RELEASE-NOTES ( wiki). įor more information, please read the Manual:Installation requirements and Compatibility. If you are using PostgreSQL, please also read Manual:Upgrading Postgres. This means that if you want to upgrade to 1.36 from 1.23 or earlier, you'll first have to upgrade your 1.23 wiki to 1.27 (or 1.35), and, from 1.27 (or 1.35), you'll be able to upgrade to 1.36. Upgrades from older versions of MediaWiki will have to be performed in multiple steps. Since Version 1.36, MediaWiki only commits to supporting upgrades from two LTS releases ago (see phab:T259771). If you are using one of these versions and can not upgrade to a newer version, please see 2021-12 security release/FAQ for a workaround. MediaWiki from 1.32 to 1.35.4, 1.36.2, 1.37.0 contain a security issue that allow unprivileged editing of arbitrary page and arbitrary JavaScript execution.
Remove leftovers from old installations.Run the update script to check the database.
0 kommentar(er)
