WackoWiki: Upgrade notices for 5.5.x

https://wackowiki.org/doc     Version: 99 (23.12.2023 10:45)

Upgrade notices for 5.5.x

Upgrade your WackoWiki from 5.x.y to 5.5.x.



See also the migration guides for WackoWiki versions 5.0.x[link1], 5.1.x[link2], 5.4.x[link3], 6.0.x[link4] and 6.1.x[link5].

1. Preparations

  1. Check Release Notes[link6] for requirements
  2. Back up your data.
    1. your wiki database (e.g. via phpMyAdmin or the backup module in the Admin Panel[link7] )
    2. your wiki folder

IMPORTANT
Backup your data! Before doing anything, backup your existing database and files. Also ensure that during migration nobody uses the database, because it may cause loss of data.
  1. It is imperative that you make a backup of your WackoWiki database before you upgrade.
  2. The upgrade procedure transfers your installation instance data from the old version to the new version. Migration from the new version back to the old version is not supported.

2. Download

  1. Download the archive[link8]
    1. Extract the archive
    2. Remove all wacko folders and files from you current installation, except
      • config/config.php
      • file/ (rename the existing folder files to file)
      • replace the old .htaccess files from the remaining folders with the new ones from the distribution package
    3. Copy the new wacko.5.5.x files in your wacko folder
  2. Pull the release[link9]
    1. Delete the cached config files under _cache/config/ before you proceed
  3. Check file permissions[link10]

3. Installer

WackoWiki R6.1 upgrade step 1: language settings
Call the URI of your Wiki in your browser. The installer starts and tells you (IMPORTANT) that you are upgrading from 5.x.y to 5.5.x

4. Post-Upgrade

The following issues apply only if you upgrade for the first time to WackoWiki 5.5.x.

4.1. Passwords

  1. You must recreate your recovery_password for your Admin panel[link7], because it uses the new password_hash() and password_verify() API, if you upgrade from a version prior to R5.5 .
  2. Call the {{admin_recovery}} action as Admin and generate a new password hash for your recovery_password.

4.2. Configuration

If you've had set custom values in constant.php, router.conf, csp_custom.conf or or otherwise, you must set or merge these values again.

4.3. Re-Synchronize data

After successful upgrade you can perform a re-rendering for all intrasite links to rebuild the records of the page_link and file_link table.

4.4. Converting Tables from MyISAM to InnoDB

If you have existing MyISAM tables, that you want to convert to InnoDB for better reliability and scalability, use the following routine.

4.5. Converting Columns to SQL strict

If you have existing tables, that you want to convert to comply with the SQL strict mode, use the following routine.

4.6. Replace the action parameter for/root with page

If you have existing actions using the depreciated parameter for=, replace it with the parameter page=, otherwise the parameter gets ignored and the default argument for page is used in the action.

5. Notes

  1. Leave a comment here if something is not clear or you have further questions.
  2. Do not hesitate to improve this instructions and the wording.