This is an old revision of the document!
Table of Contents
upgrade plugin
Compatible with DokuWiki
adora belle, weatherwax, binky, Ponder Stibbons, Hrun
This extension has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues.
Similar to elwikiupgrade
Download and Installation
Download and install the plugin using the Plugin Manager using the URL given above. Refer to Plugins on how to install plugins manually.
Changes
- Version upped (2024-02-06 23:50)
- some code style cleanups (2024-02-06 11:31)
- remove type hint for compatibility with old PHP (2024-02-06 11:19)
- upgrade test for greebo should use legacy.php (2024-02-06 11:07)
- get minimum php requirements from composer.json (2024-02-06 10:26)
- update test workflow (2024-02-06 10:10)
- Merge pull request #241 from dokuwiki-translate/lang_update_805_17065… (2024-02-06 09:47)
- translation update (2024-01-30 08:01)
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.
This plugin was only tested in upgrading from “Lemming” upwards. It might work for upgrading older versions as well.
Creating a backup (see FAQ - Backup) of your wiki before upgrading is highly recommended. It's NOT done by the plugin.
Before running this plugin, always check if a newer version of the plugin is available and upgrade the plugin first.
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.
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.