This is an old revision of Doc/Russian/Обновление from 20.02.2018 14:10 edited by WikiAdmin.


Имеется также Deutsch и English

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

1. Preparations

  1. Check ReleaseNotes 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
  3. Download
  4. Extract the archive
  5. 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
  6. Copy the new wacko.5.5.x files in your wacko folder
  7. Check permissions

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

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

  • 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
  • Screenshots from Upgrade procedure

3. Post-Upgrade

3.1. Пароли

  1. You must recreate your recovery_password for your Admin panel, because it uses now the new password_hash() and password_verify() API.
  2. Call the {{admin_recovery}} action as Admin and generate a new password hash for your recovery_password.

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

3.3. Converting Tables from MyISAM to InnoDB

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

  • Admin Panel -> Database -> Convert

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

4. 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.rade"}}

Upgrade your WackoWiki from 4.x to 5.0.x.

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


  1. Check ReleaseNotes for requirements
    1. PHP is supported only up to PHP 5.3.x
    2. you can use XAMPP 1.7.7 to upgrade your legacy application
  2. Back up your files to save important data.
  3. Download the final version.
  4. pull your site in a local htdocs/test folder
  5. get the database dump
  6. import the database dump (e.g. via phpMyAdmin)
  7. rename or remove changed default pages, the installer can only rely on the user 'WackoInstaller' in the pages table to identify and update those pages
  8. remove all files and folders under htdocs/test except wakka.config.php and files/
  9. modify the wakka.config.php so it will work with your local environment (database, path, theme, etc.)
  10. now pull / copy the repo head into the same folder (just the content of the wacko/ folder)
  11. check database tables for abandoned or inconsistent data

Call the URI in your browser -> the installer starts and tell you that you are upgrading from 4.2 / 4.3 to 5.0.x


  • go through all steps

Now you should have your upgraded Wiki. Now login as Admin and create a page called UpgradeRoutine and add there the action {{adminupdate}} -> save (the installer will try to create this page e.g. /Users/WikiAdmin/MigrateDataToR50)

Migrate data from R4.x to R5.0

Action: {{adminupdate}}

The upgrade utilities are only in this release available.


  1. convert files per page
  2. move global files to new sub folder
  3. migrate user settings
  4. update user statistics
  5. move user pages into user name space
  6. set page title based on tag
  7. set page depth based on tag
  8. set version_id for revision

adminupdate action to migrate data from R4.x to R5.0


  1. check character_set_client and character_set_connection
  2. check for empty lines in the old bookmark field if conversion of user settings fails and remove them

Renamed Actions

  • a -> anchor
  • comments -> comment
  • orphanedpages -> orphaned
  • recentchanges -> changes
  • recentlycommented -> commented
  • recentcomments -> comments
  • showparagraphs / p -> paragraphs
  • tableofcontents -> toc
  • wantedpages -> wanted

Renamed Formatters %%([formatter]) content %%

  • comments -> comment

You can use search to find the old strings and replace each with the new one.

change user links

  • ((/UserName UserName)) -> ((user:UserName UserName))
  • set in config/interwiki.conf
    user /Users?profile=
    • if your Wiki does not resides in root add the folders
      user /folder_test/wacko/Users?profile=

Edit default menu items

  • login as Admin
  • via action {{menu system=1}} you can edit the default bookmarks

Admin Panel

The new Admin panel is in Beta stage.

  • to login define the recovery_password in the config file first
    1. call ther {{admin_recovery}} action as Admin and generate the password hash for your recovery_password
    2. add the password hash: 'recovery_password' => 'add hash here',
  • Don't forget to delete the _cache/config/config.php afterwards.
  • call yourwiki/admin.php
  • enter your recovery_password

If your Admin panel gets locked, reset config/lock_ap from 1 to 0.


To use Captcha, you must ensure that the session settings in freecap.php do not differ from the default values or your config settings,
else Captcha can't pass its values to the session. In the following link you find a workaround for this from our Development-Blog:


  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.
  3. It is intended to remove all upgrade and legacy code prior to 5.0 after this release.

5. сделайте резервную копию файлов и БД

  1. скопируйте новые файлы ваки поверх старых*
  2. зайдите на ваку, проделайте предложенную процедуру обновления
  3. всё.

* Если в старой версии ваки вы 

  1. создали новую тему из существующей
  2. не переименовали её

то тему вам придётся восстанавливать из упомянутой вначале резервной копии и переделывать.