Table of Contents
upgrade Plugin
Compatible with DokuWiki
- 2024-02-06 "Kaos" yes
- 2023-04-04 "Jack Jackrum" yes
- 2022-07-31 "Igor" yes
- 2020-07-29 "Hogfather" yes
Similar to elwikiupgrade
Download and Installation
Search and install the plugin using the Extension Manager. Refer to Plugins on how to install plugins manually.
Changes
- Version upped (2025-04-11 01:11)
- supress warnings from opcache_reset() (2025-04-10 14:10)
- Merge pull request #255 from dokuwiki-translate/lang_update_977_17303… (2024-11-08 09:15)
- translation update (2024-10-31 12:05)
- Merge pull request #254 from dokuwiki-translate/lang_update_968_17290… (2024-10-30 09:22)
- translation update (2024-10-16 08:10)
- Merge pull request #245 from dokuwiki-translate/lang_update_853_17157… (2024-07-29 08:17)
- translation update (2024-05-15 14:40)
Usage
This plugin adds a new option to your admin interface called “Wiki Upgrade”. Follow the wizard and upgrade your wiki to the most current stable release of DokuWiki in just a few steps.
Note: this plugin needs write access to all your DokuWiki files, not only files inside data. If you installed DokuWiki through the DokuWiki Downloader, permissions should be fine already. Don't worry though, the plugin will check for needed permissions before doing the real upgrade process.
Creating a backup (see FAQ - Backup) of your wiki before upgrading is highly recommended. It's NOT done by the plugin.
Command Line
The plugin can also be used from the command line. There are two ways to do so:
- Modern wikis (post-Greebo) support command line plugins which can be called through the
bin/plugin.php
script. This is the preferred method of using the upgrade plugin. This ensures a properly initialized DokuWiki environment when upgrading. - Older wikis (tested back to a release from 2006) can be upgraded by calling
lib/plugins/upgrade/legacy.php
. This is particularly useful when the old wiki is no longer running with a modern PHP version. The legacy script does not load any existing (outdated) DokuWiki code, but will make more assumptions on your setup. Read the comments at the top of the script for more info.
Below both methods are shown. Prefer the first when possible.
Usage
To check permissions and versions, without actually updating run:
php bin/plugin.php upgrade check
php lib/plugins/upgrade/legacy.php check
To run the upgrade:
php bin/plugin.php upgrade run
php lib/plugins/upgrade/legacy.php run
Check the help screen for any addtional options:
php bin/plugin.php upgrade -h
php lib/plugins/upgrade/legacy.php -h
Q & A
Usable on systems without internet access?
The plugin downloads new releases directly from the github.com repository. Therefore it needs direct access to the internet.
Any PHP requirements?
Make sure that PHP was compiled with php_openssl enabled. Your PHP version will also need to be new enough for the new DokuWiki version to be installed (the plugin will check that for you).
I moved some folders out of the Webroot, is that a problem?
The upgrade plugin does currently not support installations where the conf
directory was moved from the default location.
If you moved the data
directory, the plugin will recreate a data
directory at the default location. That directory can be safely deleted afterwards. You may need to create any new subfolder inside your data
directory manually after the upgrade.
Upgrade to Weatherwax
Upgrade to Weatherwax using this plugin is only recommended when you're using the plain auth mechanism. Other authbackends probably need some manual config tuning.
Languages
The plugin will install the new version with all languages included. Even if you originally downloaded DokuWiki with a limited set of languages. You can use the langdelete plugin to clean up afterwards.