Hebrew characters become question marks. HELP!

[ptgptg]

Using version 2.6.4 - Hebrew
I tried to apply a fix for the admin/settings/save.php vulnerability that was mentioned on this forum. After applying, i stupidly tried to run save.php - which of course wiped my settings etc..
I DO have backup which i made from inside the admin settings (.SQL file), but when i try to restore it using PhpMyAdmin, all hebrew chars become question marks.
I've tried to play with the encoding from inside phpmyadmin - utf8 and hebrew.
Nothing helps - although sometimes i managed to see hebrew characters from inside phpmyadmin, but when i view the website it's all the same - only question marks.
Even tried to load the .sql file with notepad and save it as utf8 - nothing works.
php version 5.2.5
mysql version 4.1.22
PHPmyAdmin version 2.11.4

PLEASE help! This is frustrating...

Thanks
 

[doc]

Hello,

wait a couple of days and then upgrade to WebsiteBaker 2.7 (to be released this week) which should fix the issues with utf-8 support we had up to WB 2.6.7.

Regards Christian

[ptgptg]

thanks.
Still, maybe any one had the same problem and has an idea?

[ptgptg]

I just upgraded to 2.7.

Here goes:

1. All hebrew chars are still question marks even when i edit a page (or create a new one) and type in hebrew chars, once i press the save button it all turns to question marks.

2. In the backend, all hebrew words are reversed (ISO visual instead of windows-1252), i have to change the encoding every time i move to another section of the admin area.

3. is it safe to try to restore from the 2.6.4 sql file using phpmyadmin?

should i do anything else?

[ruebenwurzel]

Hello,

your problem is only how you import the sql file. You must import the file with the same charset as you exported it. Exporting it with hebrew charset and importing it with utf8 f.e. brakes alle special chars. So if you look in the sql file with an editor (notepad++), are the special chars in this file ok or are they broken? If they are broken in the sql file you have a problem.

You have a second problem as you already upgraded to WB 2.7. You cannot use the old backup file. Sou you have to revert back all to 2.6.4 (files and database). An upgrade to wb 2.7 is only recommanded on fully working WB installation. What doc meant was, that in all versions lower than WB 2.7 WB was buggy with all languages with special chars. This is fixed in WB 2.7. The upgrade did not repair broken pages.

Matthias

[ptgptg]

Ok,
The content of the sql file looks intact. How will i know in which charset i exported the database? I've done it from inside WB.
by looking at the line from inside the sql file: ENGINE=MyISAM AUTO_INCREMENT=34 DEFAULT CHARSET=latin1;
I can assume that the charset was latin-1?