Either (A) or (B): fix the encoding issue (5.0 or before -> 5.1 or later)

Previously to Tiki 5.1, some users might have had a double encoding issue in the database of their Tiki. To ensure that this potential problem is fixed for all, if you are upgrading from a Tiki version equal or earlier than 5.0, into some newer Tiki version (5.1, ...5.x; 6.0, 6.x...), you are encouraged to follow once the three steps to fix the issue by means of the tiki-install.php script.

1.3.1.1. Export existing database from earlier releases (< 6.0)

When dumping MySQL databases from earlier versions of TikiWiki you should specify "--default-character-set=latin1 " to ensure that your MySQL client does not double encode any existing latin1 data.

1.3.1.2. Force connection to utf-8 in db/local.php

Briefly explained above. For the sake of clearness, covered here in detail.

• Go to tiki-install.php, and follow steps until step 4: "Set the Database Connection".
• Even if you have a local.php file already there, click on "Modify database connection" instead of "Use Existing Connection". This will open a form in the lower part of the window for you
  
  

  Click to enlarge
  • At the bottom, there will be a section called "Character set", with a checkbox called "Always force connection to use UTF-8", that needs to be kept as checked.
    
    

    Click to enlarge
  
  Fill in your db/local.php details through that form, and click on the "Continue" bottom at the bottom when ready.
• Continue to step 5 in the installation process, where you'll have the opportunity to "Convert database and tables to UTF-8" (see below).

1.3.1.3. Convert database and tables to UTF-8

In step 5 of the installation process, you will be offered the option to "Convert database and tables to UTF-8", and you will be also shown the current encoding of your database.

• Write down the name of the current encoding of your database, because you will need it in the next step below.
  
  

  Click to enlarge
• You can now click on the button "Convert database and tables to UTF-8".
• Once successfully performed, you will not see this option anymore, but just the usual question of whether you want to Re-install the database, or "Automatically upgrade your existing database to" your new Tiki version. Choose this later option, since you are upgrading.
  
  

  Click to enlarge

(Note: This step is converting you DB collation to utf-8, and your DB tables to use the utf-8 charset also.)

1.3.1.4. Convert content from your previous encoding to utf-8

Finally, you need to convert the content from your existing database (content from wiki pages, etc., but also preferences, which include paths to file and image attachments, like in image galleries, etc.) to utf-8.

• To do so, you have an option in the final step under the section "Upgrading and running into encoding issues?"
  
  

  Click to enlarge
• In the dropdown called "Previous table encoding", choose the one which applies to your case (you wrote it down in the previous step), and click on the button: "Dangerous: Fix double encoding"

Given the nature of this fix, it's best to do some quick verification of the changes.

Congratulations! You are done.

You can now enter Tiki locking the installer (recommended) or without locking it, and continue using Tiki as normally.

If you have any issues, provide feedback through the usual Support channels.