??? Modx 1.0 cuts content on accents

hi. i have a problem here.

ive intstalled Modx v1.0 set Character set to Unicode (utf-8) and
SET CHARACTER SET’ method, but!

when i input text like:

"Quis nostrud exercitation sed do eiusmód tempor incididunt consectetur"

and i save the document... the output text will be;

"Quis nostrud exercitation sed do eiusm"


it cuts out the text after the accented char.

any solutions?
thanks.

Have you looked in PhpMyAdmin to see what the actual character encoding of the tables and fields is? I suspect that you’ll find some Latin1 in there. Either that, or the actual data in the fields is not UTF-8 (especially if you imported an SQL file from another site).

thxs for reply.

1.- database is set to "utf8_general_ci", shoul i change it to other?
2.- plain clean installation.

utf8_general_ci should be fine, but did you check the individual table and field containing the data that won’t display?

Quote from: BobRay at Oct 26, 2009, 02:29 PM

utf8_general_ci should be fine, but did you check the individual table and field containing the data that won’t display?

yes i did. content gets cut from the accented charracter on.

(from previous example) content on that field will be saved as:

"Quis nostrud exercitation sed do eiusm"

..and nothing else.
but if i write this way:

"Quis nostrud exercitation sed do eiusmód tempor incididunt consectetur"

..it will be saved as..

"Quis nostrud exercitation sed do eiusmód tempor incididunt consectetur"

...and displayed correctly on the frontend like this..

"Quis nostrud exercitation sed do eiusmód tempor incididunt consectetur"

:(

I have to admit that I once had the same problem and never did solve it. No one on the team could duplicate it and I finally gave up on it. I think the problem was that the actual data in the table was not in UTF-8 even though the table was set to that, but I never confimed this.

Hopefully, someone who knows more about character sets will chime in.

a strange thing about it is that on 9.6.3 i had no problem.
maybe a parser bug?

I had the problem on Revolution (but not .9.6.3) and only in the Manager. I dug through a lot of MODx code looking at things like utf8_encode() and utf8_decode(), but I couldn’t find anything that worked and, as I said, no one else could duplicate the problem. I’m not going back into that swamp unless I absolutely have to.

Most days, I think the PHP and MySQL handling of charsets is a plot on the part of old-school coders to drive everyone insane -- but maybe it’s just me.

thanks for your help bob.

i sad to say that i just had to go back to .9.6.3
although i wont delete 1.0.0 installation hoping
someone can find a solution for this issue.

hopefully this post will advise all the spanish
talking people around here of this bug.

hi guys,
I hope I am not too late to help!
I live in Spain and do a lot of spanish sites in modx and there are a few problems.
I have uploaded a zip, it contains 3 spanish language files, 1 for each of these locations:
/manager/includes/lang
/snippets/ajaxSearch/lang
/snippets/eform/lang
each file´s title is appended with something like "_forManager_" to let you know which one goes where. From what you wrote I think currently you only need the "_forManager" one but I included the others just in case you come across some other problems.

Here´s an example of what modx 1.0 has in the eform spanish language file:

I have changed to:

the ajaxSearch file is the same thing.

If you use any of these files I recommend keeping the originals in place but renaming them to old_ or something so if anything goes wrong you can revert! Shouldn´t have any problems tho, just to let you know I never had your problem of the chars with accents getting cut out, the problem I had was á would get replaced with an ? still, I now have accents displaying fine in the manager with 1.0.
Let me know how it goes, suerte.
Dan