Also available in Deutsch, Français und Русский

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

See also the migration guides for WackoWiki versions 5.0, 5.4, 5.5 and 6.1.

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. Pre-Upgrade Routines for R6.0

Skip this section if you do not upgrade from R5.5.

2.1. Convert Tables from MyISAM to InnoDB

If you have existing MyISAM tables, you have to convert them to InnoDB with the following routine.

• Admin Panel -> Database -> Convert

2.2. Convert your tables and records to UTF-8

You should run the the first part of the routines prior to your upgrade to R6.0.x.

• Database UTF-8 Conversion Script

3. Upgrade

3.1. Download

1. Download wacko.6.0.x.zip
2. Extract the archive
3. Delete all wacko folders and files from you current installation, except
   • config/config.php
   • file/
4. Copy the new wacko.6.0.x 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.

3.2. Installer

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

• go through all steps
• Screenshots from Upgrade procedure

4. Post-Upgrade

4.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.

4.2. 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.

• 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.

4.3. Unicode transition issues

Skip this section if you do not upgrade from R5.5.

The migration to Unicode is an ongoing process. It may require manual adjustments over a longer period of time. Below we will share our experience, findings and possible solutions.

4.3.1. Replace old transliterated links and supertag references

Before you run any SQL UPDATE command create a backup beforehand. One error and you may loose all your data.

UPDATE prefix_page SET body = REPLACE(body, '/Doc/Русский/Obnovlenie', '/Doc/Русский/Обновление');	

1.  ((!/el ÅëëçíéêÜ @@el)) -> ((!/el Ελληνικά))	

2.  ((/Doc/Русский/Obnovlenie ru)) -> ((/Doc/Русский/Обновление ru))	

3. file:/forum/discussion/ifmodifiedsinceheaderdoesnotworks/403_network_analysis.png
    -> 
   file:/Forum/Discussion/IfModifiedSinceHeaderDoesNotWorks/403_network_analysis.png	

Alternatly the {{admin_replace}} action can be used to replace these strings.

Set back body_r afterwards, so the parser re-renders the pages with the changed content.

UPDATE prefix_page SET body_r = '';	

4.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 or database changes.

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

5. 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.