[Solved] Headers Error after Logging In

Now I get the following warning both at the top of the
login page and then on a blank page once I have entered
my username and passoword.

Warning: Cannot modify header information - headers already sent by (output started at /home2/mercolog/public_html/modx-base/manager/includes/lang/spanish.inc.php:1) in /home2/mercolog/public_html/modx-base/manager/index.php on line 168

I know that this error happens when there are extra spaces before or after the
php tags, and it is fixed by removing them.

In this case it is in line 168, where the header is being sent:

// send the charset header
header(’Content-Type: text/html; charset=’ . $modx_manager_charset);

NO clue on how to fix this...

Make sure you don’t have extra spaces in your language file after the closing ?> ... I fixed a whole boatload of those for 1.0.1 (to be released in the coming weeks). Could be another file too of course.

Nope, no extra spaces in language file or index.php file.
Mmmm...

What is the 1 in spanish.inc.php:1 ?

Does it matter that the index.php file does not end in ?>
it just kindof ends after a debug call...

That error means that MODx can’t set the headers because the error message already did. The actual error is in the Spanish language file on line 1.

PHP files do not need to have a closing ?>; many programmers omit this because if somehow another space or return gets added after it there will be an error.

All is OK in line 1, these are the first few lines in the spanish.inc.php file:



so I STILL do not know how to proceed with launching the manager...

I tried updating the installation choosing english as the languge to see if
it was the Spanish file, but the same error appeared...

next step would be to uninstall and install again... to see if it works...
or do anybody has another idea?


I kinda knew the second question, because of what you say and because the closing ?> can be located
in another file...

Problem fixed, seems too odd, I just changed the charset variable in
the Spanish file from utf-8 to UTF-8 and puff! like magic it fixed my
problem... weird... but it worked!

Sounds like something flaky in the original uploaded file itself, perhaps a bad linefeed character, and saving the file from your editor fixed it.

That is not from the latest Evo file, since the only distributed translation is iso-8859-1. Your "utf-8" isn’t a valid charset for doctypes whereas "UTF-8" is and I would suspect that would break all sorts of things actually as you found out. Where did you get the UTF-8 translation?

Yes Ryan, you are right...

Lucianno posted in the Spanish forums that he was having problems
with the encoding, so I converted the files to utf.... ejem.... UTF-8 and
uploaded the two files to JIRA as MODX-1095 http://svn.modxcms.com/jira/browse/MODX-1095.

We had a short discussion as of having both ISO-8859-1 and UTF-8,
but as UTF-8 works perfect we think we should just use UTF-8.

UTF-8 is definitely the preferred way to go, no doubt! Thanks for the update and sorry for my confusion.