Two issues when upgrading to 0.9.6.1

MODX Staff
10,725 Posts

opengeek Reply #11, 17 years, 6 months ago

To confirm, is the actual Charset value set this way in the response headers, too? i.e. Content-Type: text/html; charset=UTF-8 -- regardless of what you have in the source, what really matters to most browsers is the actual header being received...

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

616 Posts

mmjaeger Reply #12, 17 years, 6 months ago

Quote from: OpenGeek at Dec 10, 2007, 03:50 PM

To confirm, is the actual Charset value set this way in the response headers, too? i.e. Content-Type: text/html; charset=UTF-8 -- regardless of what you have in the source, what really matters to most browsers is the actual header being received...

how can I check that?

MODX Staff
10,725 Posts

opengeek Reply #13, 17 years, 6 months ago

I personally use the Fx WebDeveloper toolbar and select Information --> View Response Headers.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

616 Posts

mmjaeger Reply #14, 17 years, 6 months ago

is it this what you were looking for:

Date	Mon, 10 Dec 2007 16:06:09 GMT
Server	Apache/2.2.4 (Win32) PHP/5.2.1
X-Powered-By	PHP/5.2.1
P3P	CP="NOI NID ADMa OUR IND UNI COM NAV"
Cache-Control	private, must-revalidate
Set-Cookie	SN475cfdb581849=gvfl5p0t4faas0krgeiv8m1b54; path=/sites/trade.ch/ Language=de; expires=Mon, 17-Dec-2007 16:06:09 GMT; path=/
Keep-Alive	timeout=5, max=91
Connection	Keep-Alive
Transfer-Encoding	chunked
Content-Type	text/html; charset=UTF-8

MODX Staff
10,725 Posts

opengeek Reply #15, 17 years, 6 months ago

Next step, do the actual tables in the database have the proper collation? And if so, when you look at the data in phpMyAdmin using a utf8 connection charset setting, does the data appear properly?

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

616 Posts

mmjaeger Reply #16, 17 years, 6 months ago

all tables are set to MyISAM utf8_general_ci - the content appears like this

FÃ¼hrerschaft

instead of

Führerschaft

for instance

MODX Staff
10,725 Posts

opengeek Reply #17, 17 years, 6 months ago

In phpmyadmin it appears that way??!

Also, I’m willing to bet that having the db set to utf8_unicode_ci while the tables have utf8_general_ci could be the problem. Try changing the db collation to match the actual collation on the table columns it contains.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

616 Posts

mmjaeger Reply #18, 17 years, 6 months ago

yes

MODX Staff
10,725 Posts

opengeek Reply #19, 17 years, 6 months ago

Also, I’m willing to bet that having the db set to utf8_unicode_ci while the tables have utf8_general_ci could be the problem. Try changing the db collation to match the actual collation on the table columns it contains.

(Sorry, I edited the answer after you posted yes, so thought I’d repost since you didn’t reply to this part...)

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

616 Posts

mmjaeger Reply #20, 17 years, 6 months ago

Quote from: OpenGeek at Dec 10, 2007, 05:21 PM

Also, I’m willing to bet that having the db set to utf8_unicode_ci while the tables have utf8_general_ci could be the problem. Try changing the db collation to match the actual collation on the table columns it contains.

(Sorry, I edited the answer after you posted yes, so thought I’d repost since you didn’t reply to this part...)

is there an easy way to change all the table to utf8_unicode_ci using phpmyadmin