Upgrade notices for 6.0.x

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



See also the migration guides for WackoWiki versions 5.0.x, 5.1.x, 5.4.x and 5.5.x.
Unicode

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

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

Ensure you run the latest R5.5.16 release of the R5.5 branch, an upgrade from earlier versions is not supported.
Run the following routines in your WackoWiki R5.5.16 before you upgrade to R6.0.x.

2.1. Converting 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

database UTF-8 conversion script

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

3. Download

  1. Download the archive
    1. Extract the archive
    2. Remove all wacko folders and files from you current installation, except
      • config/config.php
      • file/
    3. Copy the new wacko.6.0.x files in your wacko folder
  2. Pull the release
    hg pull https://bitbucket.org/wackowiki/wackowiki-stable -r 6.0.rc1
    1. Delete the cached config files under _cache/config/ before you proceed
  3. Check file permissions

4. Installer

Screenshot: WackoWiki R6.0 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.5.x to 6.0.x

5. Post-Upgrade

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

5.1. Configuration

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

5.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
tune the re-rendering settings to avoid timeouts or reaching the memory limit

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.

5.3. Replace old transliterated links and supertag references

UPDATE prefix_page SET body = REPLACE(body, 'source:wacko', 'source:default/wacko');


possible cases
  1.  ((!/el ÅëëçíéêÜ @@el)) -> ((!/el Ελληνικά))
  2.  ((/Doc/Russian/Obnovlenie ru)) -> ((/Doc/Russian/Обновление ru))
  3. file:/forum/discussion/ifmodifiedsinceheaderdoesnotworks/403_network_analysis.png
     -> 
    file:/Forum/Discussion/If-Modified-SinceHeaderDoesNotWorks/403_network_analysis.png

set back body_r so the parser re-renders the pages with the changed content
UPDATE prefix_page SET body_r = '';

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