1
kalamata
Encoding broken after database restore
  • 2009/3/2 13:50

  • kalamata

  • Not too shy to talk

  • Posts: 121

  • Since: 2005/3/3 1


Dear All,

I am having the following problem: set the encoding of my page to Greek (88957) and everything was working perfectly until I had to move the site to a different server. I restored the database and re-installed as usual, but the database content, as well as the template content (I had made changes to the template file for the main menu as well) is broken; I get funny characters instead of my text.

This is affecting the whole site (have modules for photos, forum etc) and I am at a loss as to what to do - retrieving the data will take ages and in some case (forum posts) will be impossible.

Do you have any idea as to what I might try?

Regards,
George

2
ghia
Re: Encoding broken after database restore
  • 2009/3/2 14:21

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Quote:
and re-installed as usual
We are not aware of your habbits. Do you mean XOOPS? Version?

3
kalamata
Re: Encoding broken after database restore
  • 2009/3/2 14:43

  • kalamata

  • Not too shy to talk

  • Posts: 121

  • Since: 2005/3/3 1


Hi,

Thanks for the prompt reply. It is XOOPS 2.0.18.1 and by as usual I mean back-up and restore through phpMyAdmin and editing the mainfile.php file to reflect the changes in URL and server paths (I just put as usual, because I have done it so many times).
MySQL is 5.1.31 and PHP is 5.2.8.

Let me know if you need any further details.

Regards,
George

4
ghia
Re: Encoding broken after database restore
  • 2009/3/2 15:15

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Is ISO-8859-7 present in the value for HTTP_ACCEPT_CHARSET in phpinfo() (Apache environment)?
I suppose your database tables character set and collation is greek and greek_general_ci? And greek is also your XOOPS_DB_CHARSET (in mainfile.php)?
What settings do you have in /languages/greek/global.php (last 3)?

5
kalamata
Re: Encoding broken after database restore
  • 2009/3/2 17:23

  • kalamata

  • Not too shy to talk

  • Posts: 121

  • Since: 2005/3/3 1


Hi,

Many thanks again for replying so promptly. I am not sure what you mean with HTTP_ACCEPT_CHARSET - is it HTTP_ACCEPT_LANGUAGE? If yes, it is en-gb,en;q=0.5.

I do not have greek as the main XOOPS language, but my settings in /languages/english/global.php are ISO-8859-7, el and 0 for mutli-bytes.

There is no XOOPS_DB_CHARSET, though, in mainfile.php, unless you are referring to something else.

You are absolutely right about the character set and collation variables.

Regards,
George

6
kalamata
Re: Encoding broken after database restore
  • 2009/3/9 20:33

  • kalamata

  • Not too shy to talk

  • Posts: 121

  • Since: 2005/3/3 1


Could somebody possibly shed some light on this one? It is really frightening not knowing whether your database would be restored correctly due to unknown issues.

Regards,
George

7
Catzwolf
Re: Encoding broken after database restore
  • 2009/3/10 4:29

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


Could you give us a link to your website?

8
kalamata
Re: Encoding broken after database restore
  • 2009/3/10 14:01

  • kalamata

  • Not too shy to talk

  • Posts: 121

  • Since: 2005/3/3 1


Quote:

by catzwolf_ on 2009/3/10 5:29:42

Could you give us a link to your website?


Sure, have a look athttp://www.n-d.seflshop.org.uk/ndphotos/ (it is the section with the photos, fixed some stuff manually so that the site is readable). This section was fine on the previous server, but now it appears illegible. Any advice would be greatly appreciated (apologies for the late reply, was 3am UK time when you posted the last reply).

Regards,
George

9
Catzwolf
Re: Encoding broken after database restore
  • 2009/3/10 14:10

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


lol no problems, I'm from the UK myself. I sleep funny hours ;)

10
Catzwolf
Re: Encoding broken after database restore
  • 2009/3/10 14:37

  • Catzwolf

  • Home away from home

  • Posts: 1392

  • Since: 2007/9/30


fyi, XOOPS 2.018 doesn't use the XOOPS_DB_CHARSET.

Okies, I have had a look at your source code and I see no problem with your metatags etc.

I'm not sure what is going on, but either check what charset the database is using for the tables, or it could be a server configuration problem?

Did you try using 'windows-1253'? (Stab in the dark there ;) )


Login

Who's Online

148 user(s) are online (116 user(s) are browsing Support Forums)


Members: 0


Guests: 148


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits