View source for Upgrade notices for 5.5.x

Upgrade your WackoWiki from **!!(green)5.x.y!!** to **!!(green)5.5.x!!**.

{{toc numerate=1}}

See also the migration guides for WackoWiki versions ((/Dev/Release/R5.0/Upgrade 5.0.x)), ((/Dev/Release/R5.1/Upgrade 5.1.x)), ((/Dev/Release/R5.4/Upgrade 5.4.x)) and ((/Dev/Release/R6.0/Upgrade 6.0.x)).

===Preparations===
  1. Check ((/Dev/Release/R5.5/ReleaseNotes Release Notes)) for requirements
  1. **Back up your data**.
    1. your **wiki database** (e.g. via phpMyAdmin or the backup module in the ((/Doc/English/AdminPanel Admin Panel)) )
    2. your **wiki folder**

%%(info type="important")
**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.
  2. It is imperative that you make a backup of your WackoWiki database before you upgrade.
  3. 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.
%%

===Download===
  1. ((/Download Download the archive)) 
    3. Extract the archive
    4. 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
    1. Copy the new wacko.5.5.x files in your wacko folder
  2. ((/Org/Tools/Repository Pull the release))
    6. Delete the cached config files under ##_cache/config/## **before** you proceed
  6. Check ((/Doc/English/FilePermissions file permissions))


===Installer===
file:/wackowiki_r55_en_upgrade_1.png?right&400&caption
Call the URI of your Wiki in your browser. The installer starts and tells you (IMPORTANT) that you are **upgrading** from **!!(green)5.x.y!!** to **!!(green)5.5.x!!**
  * go through all steps
  * **Data base configuration**: If the installer asks you for charset, select the appropriate character set 
    * cp1251 Windows Cyrillic
    * cp1252 Western European
    * ISO 8859-2 Central European
    * ISO 8859-7 Greek
  * ((/Doc/English/Upgrade/Screenshots Screenshots from Upgrade procedure))

===Post-Upgrade===
The following issues apply only if you upgrade for the **first time** to  WackoWiki **!!(green)5.5.x!!**.

====Passwords====
  1. You must **recreate** your ##recovery_password## for your ((/Doc/English/AdminPanel Admin panel)), 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##.

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

====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

====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. 
  * Admin Panel -> Database -> Convert

====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.
  * Admin Panel -> Database -> Convert

====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.
  * e.g. ##""{{changes for="Dev"}}""## -->  ##""{{changes page="Dev"}}""##

===Notes===
  1. {{comment text="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.