Thread

I’m running EE 1.6.0
recently I moved my website to a new server, but the text encoding after the migration was wrong.
the web site is in arabic, the encoding of the data is 8-utf.
is there any way I can solve this issue? even if it’s a paid migration service?

Hi, EYEWEAVER. Ingmar is one of our TSS team. He has the most experience in working with encoding issues. I may need to consult with him about your issue.

What was the encoding *before* the move?

The encoding was 8-utf
this encoding issue with EE is really weird! it’s not affected whatsoever by the encoding I put in the html templates as if it has a mind of its own!
I hope Ingmar can help me with this issue, otherwise I’ll have to publish all my content again from scratch!

How about a link to the site?

Hi Eyeweaver 😊 As Sue said, a link to the site would be most helpful. Even though the “encoding of the data” may be 8-utf” as you say, could it be that it used to be a different encoding? Also, EE 1.6.0 is very old, do you think you could upgrade to the latest version and build?

Hi Ingmar

the website is http://www.haridy.com
the encoding used to be 8-utf, and u can have a look on the site on the old server on this url:
http://www.haridy.ws

as for upgrading, I’d rather move the site to the new server successfully first the upgrade 😊
Thank you for your help 😊

haridy.ws forwards to haridy.com/cms/ as does, haridy.com. I would be most interested in seeing the old site, though.

try :
http://www.haridy.ws/cms
😊

Well, it’s like I expected:

<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">

Your data is probably encoded with that charset. Try changing your new website to that as well.

this code is from the old site or the new site?
the old site is in 8-utf, but the data in the new site is in windows-1256 for a reason I don’t know!
the problem is, the windows-1256 encoding option is not available in the control panel in EE!

This is from the old site at http://www.haridy.ws/cms, where you have:

<!--
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 
//-->
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">

ie utf-8 being commented out in favor of windows-1256. If windows-1256 is not available in EE’s control panel, you simply need to add

<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">

to your templates.

I did add it to the template, and it has no effect at all.. as I told you, as if EE encoding has a mind of its own!
I even tried to over ride the encoding from the apache server configuration to force the windows-1256 encoding on all pages.. but still no effect!
this issue happened when I first launched my web site.. every thing was fine when I was working with EE on my local machine, but once I moved it to the actual online server, I faced the encoding problem, and the only solution I found back then was to re publish all the content from scratch on the online server.

EYEWEAVER, Ingmar is correct, the encoding needs to be set to windows-1256.

How are you specifying the charset in the templates?

well.. I’ve changed it in the template.. check http://www.haridy.com, you’ll find that the problem is still there although encoding in the html is windows-1256

About the only thing I’d suggest is to reduce the template to just display the exp:weblog:entries code with the proper encoding.

In other words, reduction testing.