Upgrade your WackoWiki from 6.0.x to 6.1.x.

See also the migration guides for WackoWiki versions 5.5.x and 6.0.x.

1. Preparations

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

2. Upgrade

Requires at least WackoWiki 6.0.22, if you use a earlier version upgrade to this version first or later, before you upgrade to WackoWiki 6.1.

2.1. Download

1. Download wackowiki-6.1.x.zip
2. Extract the archive
3. Delete all wacko folders and files from your current installation, except
   • config/config.php
   • file/
4. Copy the new wacko.6.1 files in your WackoWiki installation folder
5. Delete the cache file under cache/config/config.php.
6. Check file permissions

If you have created custom themes, actions, handlers or formatters in the old version of WackoWiki, then you need to restore them from the backup you made at the beginning. Check their compatibility and fix them if necessary.

2.2. Installer

Call the URI of your Wiki in your browser. The installer starts and tells you (IMPORTANT) that you are upgrading from 6.0.x to 6.1.x

• go through all steps
• Screenshots from Upgrade procedure

3. Post-Upgrade

3.1. Configuration

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

3.2. Re-Synchronize data

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

• Admin Panel -> Synchronizing data -> Wiki-links

You can tune the re-rendering settings to avoid timeouts or reaching the memory limit. This is mostly interesting for shared hosting or servers you do not manage. The server terminates then the script without further notice.

If the re-rendering fails just reduce the number of pages it renders per turn, the redirect LIMIT is set to 10. If you reach the redirect limit the script will provide you with a link Next », which you have to click to render the next batches of pages. Furthermore avoid possible session timeouts while the script is running.

3.3. Changes

1. Writes now the sitemap.xml into the xml/ folder, please check and update your robots.txt, e.g.

   • Sitemap: https://wiki.example.com/xml/sitemap.xml.gz	

2. Requires now the ICU Dates and Times Format used by IntlDateFormatter, please update your custom settings in the Admin panel.

   • config	DateTime::format	IntlDateFormatter
     date_format	d.m.Y	dd.MM.yyyy
     time_format	H:i	HH:mm
     time_format_seconds	H:i:s	HH:mm:ss

3. To create the file hashes for files uploaded prior to WackoWiki 6.1.19 use the {{adminupdate}} action.
   • Set missing file hash for legacy records in file table
4. Remove the backups you've created prior to WackoWiki 6.1.21 from the file/backup/ folder or replace the backup.log with a JSON formatted version.

   • {
         "cluster": "",
         "data": "wacko_acl;wacko_auth_token;wacko_config;wacko_category;wacko_category_assignment;wacko_external_link;wacko_file;wacko_file_link;wacko_menu;wacko_page;wacko_page_link;wacko_revision;wacko_user;wacko_user_setting;wacko_usergroup;wacko_usergroup_member;wacko_watch",
         "files": "file/global;file/perpage",
         "size": 104080339,
         "structure": "wacko_acl;wacko_auth_token;wacko_cache;wacko_config;wacko_category;wacko_category_assignment;wacko_external_link;wacko_file;wacko_file_link;wacko_log;wacko_menu;wacko_page;wacko_page_link;wacko_referrer;wacko_revision;wacko_user;wacko_user_setting;wacko_usergroup;wacko_usergroup_member;wacko_watch",
         "time": 1681202531,
         "wacko_version": "6.1.21"
     }	

3.4. Custom themes, actions, formatters, handlers and other modifications

Do not forget to update and check your own modifications and extensions. Look out for changed functions, database changes or CSS changes.

1. Please look in the community folder or Patches section for available updates.
2. Merge possible core changes in your own theme

4. Notes

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