[Brian]

When you go into System Config -> Advanced Settings, do you see any entries for MySQL?

Thanks!

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation

[fer]

bigguy:

When you go into System Config -> Advanced Settings, do you see any entries for MySQL? Thanks! - Brian

I can see:

jr_db_charset -> utf8
jr_db_collate -> utf8_unicode_ci

[Brian]

fer:

bigguy: When you go into System Config -> Advanced Settings, do you see any entries for MySQL? Thanks! - Brian I can see: jr_db_charset -> utf8 jr_db_collate -> utf8_unicode_ci

Good - that means your database is storing the data as UTF8 (which is what we want). Is your character set still set to UTF-8 throughout? We want to make sure you are using UTF8.

Is it just on the comments that you see it not working properly?

Thanks

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation

[fer]

I just re-installed Jamroom. I haven't changed any settings.

I checked Admin Tools > database Admin . The characters in "jamroom_comments" table are correctly stored, like this -> á é í etc..


If you go here http://www.rankingargentino.com/ you can see in "Last Articles" section, that the accented characters in title dissapears, but not in the content, in the content the characters are shown properly.

If you go here http://www.rankingargentino.com/Punk_Band/ you can see that accented characters are replaced for strange characters


Thanks for helping me

[Brian]

Those all are loaded via AJAX, which was my suspicion. I think I understand what is happening here and will check it out. Basically the AJAX call is not "inheriting" the character set of the page the data is being loaded into, and will need to be specified. I'll try to get a fix online for it by this weekend if that is the case.

Thanks!

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation

[fer]

bigguy:

Those all are loaded via AJAX, which was my suspicion. I think I understand what is happening here and will check it out. Basically the AJAX call is not "inheriting" the character set of the page the data is being loaded into, and will need to be specified. I'll try to get a fix online for it by this weekend if that is the case. Thanks! - Brian

Thank you very much!

[Brian]

If you get a chance and can download the latest Jamroom Core testing 4.2.2 release:

http://www.jamroom.net/Downloads4_Test

and let me know if that helps, that would be great. You may need to delete and re-enter any created articles.

Hope this helps!

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation

[fer]

bigguy:

If you get a chance and can download the latest Jamroom Core testing 4.2.2 release: http://www.jamroom.net/Downloads4_Test and let me know if that helps, that would be great. You may need to delete and re-enter any created articles. Hope this helps! - Brian

Hi Brian,

The issue still there.

Profile comments: á --> á --> http://www.rankingargentino.com/Punk_Band
Last articles title: á --> dissapears --> http://www.rankingargentino.com
Last articles entry: á --> á (correct) --> http://www.rankingargentino.com


Do you think maybe is a server or database problem? Because when I write in Nova Demo page, the characters are shown correctly.

Thanks

PD: Maybe this can help you, I've take a print screen of 2 tables, and my database and Jamroom settings --> http://www.rankear.byethost15.com/tables.png

[Brian]

fer:

Do you think maybe is a server or database problem? Because when I write in Nova Demo page, the characters are shown correctly.

Yes - it is either a database issue or a charset issue - unfortunately it is not always easy to figure out which it is.

Quote:

PD: Maybe this can help you, I've take a print screen of 2 tables, and my database and Jamroom settings --> http://www.rankear.byethost15.com/tables.png

That image doesn't show me the table info - can you re-upload it or upload the correct one?

Thanks!

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation

[fer]

Sorry, I've re-uploaded it http://imgur.com/Yv1mX.png

Thanks

[fer]

Could you see the picture? I've re-uploaded it

[Brian]

I'm thinking you might need to change your database collation to cp1252 (from utf8) - is that an option for you in your control panel? At this point I really don't know why it's is not working for you - I can only guess that your hosting provider does not have all of the proper libraries setup on the server to fully handle UTF8 - there's nothing "special" about the hosting demo.jamroom.net is on, but if it is working there for you, then I have to assume it's not a Jamroom issue.

Sorry!

- Brian


_________________
Make sure and check out:
* The Jamroom FAQ
* The Jamroom Documentation

[fer]

I can see cp1250, cp1251 but not cp1252.


I've noticed that the information is correctly displayed when is stored in database like this ->

"<p> &aacute; &eacute; &iacute; </p>" (with entities)

So, the issue appears only in certain tables, for example "comments"


I don´t know why in some tables the information is stored like that, and other tables the information is stored with accented characters.

What a pity

If you need my Jamroom or ftp password and username to check something, please let me know


Thank's, Fer.

[fer]

well.. this is confusing..

If I set:

jr_db_charset = utf8
jr_db_collate = utf8_unicode_ci

..and write a comment, "á" is displayed "á"

but If a change to:

jr_db_charset = iso-8859-1
jr_db_collate = utf8_unicode_ci

and refresh the page, the comments are modified and "á" is displayed "á"

that's great, but when I try to comment again with this new setting.. "á" is displayed "á"


Definetly it's a charset/database issue. If I could get all "á" be stored like entities "& aacute" in database, I think that would solve the problem, but I don´t know if that's possible.

Any ideas?

[fer]

Great news !!!

After reading, reading and reading again a lot of forum topics, I found another guy have had the same problem..

The solution:

smith.kyle:

I fixed the charset problem so it should be working now. I found that everything was set properly in Jamroom, and that this was actually a server issue. The reason that the charset could not be changed from anything but Windows-1251 is that the default_charset for his server's PHP was set to Windows-1251. This could not be overridden by standard HTML meta tags for the charset. As a result, I added the following line to his .htaccess file to override PHP's default_charset: php_value default_charset utf-8 And set it to UTF-8, so everything should be working properly now. Kyle

So.. I just added the line "php_value default_charset utf-8" in my .htaccess file, and now everything works perfectly!



Thank's Brian and Kyle