Features / Usability

I read https://doc.tiki.org/Upgrade#If_you_need_to_fix_the_encoding_issue. They seem familiar. I think I did this in my upgrade from 4 to 6.

I created a copy of my 9.2 instance and performed all of these steps again. I believe I followed all the instructions correctly. I did not get an "encoding issue" warning is step 5 of tiki-install.php (evidence I did do this once before). I proceeded as if it had said latin1, including the "fix double encoding" step. I know it was latin1 when it was created. I also tested to confirm latin1 is still the default used when I create a new database via cPanel on my shared host.

The only difference between this test and my first migration to 11.2 is in the "Set the database connection" step in the "Character set" section. Here it says for the enforce UTF-8 setting "Highly recommended for new installations. However, if you are upgrading or migrating a previous tiki database, you are recommended to uncheck this box". This contradicts the instructions in https://doc.tiki.org/Upgrade#If_you_need_to_fix_the_encoding_issue. I unchecked this box in my first migration. In the this most recent test I left it checked.

The results are nearly the same. Instead of a blank page when I edit, everything after the first special character is gone. Again, if I save it in this state and rollback to the prior state, everything is restored.

Very odd.