Answered Error in lexicon "es" - headers already sent by - Blank space in top and layout issues.

I have this error in several sites. I install modx in English language, because if i select español thow me errors.

While developing i use the manager in english, but when i finish i turn the language ( in system config ) to spanish, then it start to left a blank space on top ( attach screenshot ) and the forms fields looks weird ( attach screenshot ).

In the error log appear this:

[2014-04-25 10:12:41] (ERROR @ /home/"websitename"/public_html/core/model/modx/processors/system/config.js.php : 98) PHP warning: Cannot modify header information - headers already sent by (output started at /home/caes/public_html/core/lexicon/es/resource.inc.php:1)

This error appear several times, if i refresh the page it goes out, then it happens again ( if i clear cache it happens always ), it´s not a critical error in terms of usability, but it not a good thing.

This happens in ALL WEBSITES i have created.

Any help appreciated!

Sebastián.

It could be a character set issue. More info here: http://bobsguides.com/convert-db-utf8.html

Thanks for your reply Bob!

I always use utf8_spanish_ci as character set, it displays correctly all the special characters from spanish, like ñ, ´, etc.

In the db i have set the tables and fields to utf8_general_ci, reading carefully your article and using your php file i change sucessfully the character set to utf8_spanish_ci. The problem still persist, not always, sometimes.

Thanks

Quote from: BobRay at Apr 25, 2014, 03:42 PM

It could be a character set issue. More info here: http://bobsguides.com/convert-db-utf8.html

Make sure the character set in the core/config/config.inc.php file matches what's in the DB.

There could also be a syntax error in one of your Spanish lexicon files. That would throw a PHP error and cause the "Headers already sent" issue.

I had those symptoms once from a lexicon file with a line like this:



You might turn on Chrome Dev. tools (Ctrl-shift-i) and make the error occur. Then look on the network tab. Click on a file at the left and then on the Response tab on the right. Normally, you'll see the JSON response from a processor. If you can find one that instead looks like gibberish, it may be a formatted PHP error. If you look closely at it, there will be an error message in there somewhere that may give you a clue about what's happening.

Thanks for your reply Mark!

I think is a lexicon error that comes from the pack, because i never could install Modx in spanish, always throw an error similar to this ( headers already sent by... ). I don´t see the space in the code you tell ( attach file, same as default )... what i see is that spanish lexicon is not complete, if you compare files english have much more lines of code ( not for description lenghs ), and some variables are missing in the spanish lexicon, this takes to empty buttons ( no text assigned ) or missed text description in some modx manager. I made a translation of some files one time, but they are so many files and many lines of code that i don´t have time to finish.


Quote from: markh at Apr 29, 2014, 07:03 PM

Looks like that lexicon has a space (or a BOM mark) which will cause that https://github.com/modxcms/revolution/pull/11335

An incomplete lexicon file shouldn't cause any problems. MODX should substitute the English language strings for any missing keys. In theory, the only way to get missing strings in the Manager is if the lexicon file has empty entries like this:



Only a file that throws a PHP error when "included" should cause trouble.

The first character looks like a BOM (Byte Order Mark), which doesn't show up in your typical editor, but it does screw things up

Thanks for your reply Mark!

I see, ok, i don´t see it in dw, or SublimeText.. how can i fix it?


Quote from: markh at May 05, 2014, 06:01 AM

The first character looks like a BOM (Byte Order Mark), which doesn't show up in your typical editor, but it does screw things up