SMF Support > SMF 2.0.x Support

index.english-utf8.php is missing

<< < (8/8)

frakme:
I kind of gave up on this problem and was ready to say screw it. Then the website owner came back from vacation and schooled me a little bit. She fixed the problem and gave clear step by step instructions while we worked.   The solution sounds like a lot of work but it really was just a basic "clean install" of smf 2.02. It really only took about 2 hours total and that was only because we had so many tables to go through.

Solution
1) create new empty database
2) export data and structure of current "live" database to hardrive of local computer
3) open in Emeditor, checked for any incorrect syntax or mixed collation
4) save as with encoding set to UTF8; then import into newly created database

At this point, she verified that all charsets and other information were correctly collated in phpmyadmin. Website was set to new database. Characters were still appearing garbled on website.

4) create new empty database
5) looked through index, ini and source php files, stored on host server, to make sure all charsets were set to utf8, finding no errors we went on to the next step
6)  deleted all SMF files from hosting directory/server
7) manually installed SMF 2.02, onto host server, using filezilla to create clean live site
8) dropped single table and imported same table from exported file of the old database
9) double checked that collation for rows of each table (by looking in structure tab of phpmyadmin) and table column (by using operation tab for each table) was still set to utf8 general ci
10) repeated for each standard table
11) used SMF package manager on cpanel to add packages
12) dropped single package tables and imported same table from exported file of the old database
13) Characters appear correctly

She said she could have probably imported the entire database at once, verified the collation and it would have worked fine. But she also said she wanted to double check their wasn't some weird error in any single table since the errors appeared suddenly. It is her belief that "at some point during the original upgrade via the hosting panel, something broke." At least that is a way to explain why all the information /communication was correctly coded/collated but errors still appeared.

Navigation

[0] Message Index

[*] Previous page