On server some errors on clean install

[fourroses666]

I have installed evo 1.0.12 and 1.0.13 pre release just today on a server I normally don't work with. There are some header already send messages.

I have the idea it is a very secure server and trowing out messages because of deprecated (standard) plugins etc.

When I check console in Chrome:
event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
(and a mootools error)

Found in:
/assets/plugins/tinymce/tiny_mce/tiny_mce.js
/assets/plugins/managermanager/js/jquery.min.map

I have no knowledge about this stuff but maybe some plugins need a check for deprecated code?

Could be I'm talking rubbish and this server really sucks

[Jako]

Those javascript warnings are not a big problem and should go away if Evo uses a newer jQuery version.

The line 740 does not exist in save_content.processor.php in latest Evo 1.0.13. If that error occurs in this version, please reopen the issue.

[fourroses666]

On this server it is a problem because I can't save any page. :(
Do you know what js file do I need to upgrade?
/public_html/assets/js/jquery.min.js <-- 1.8.3 to 1.9.1 didnt work

Its on line 667 with evo 1.0.13:
Warning: Cannot modify header information - headers already sent by (output started at /home/xxx/domains/xxx.org/public_html/manager/includes/document.parser.class.inc.php:1008) in /home/xxx/domains/xxx.org/public_html/manager/processors/save_content.processor.php on line 667

///////

Checking Chrome console I see:
event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
index.php?a=1&f=menu:1

Thats the only left over error

[fourroses666]

Maybe the nine lines of whitespaces is no good?
(i'm no expert :)

[Jako]

Please don't concern with event.returnValue or any javascript problems. It is not important for the header issue.

It is a PHP problem on server side. The problem occurs in $modx->evalPlugin but it is a result of a plugin issue below the error reporting level. Change line 1008 in document.parser to

die($this->messageQuit('PHP Parse Error', '', true, $type, $file, 'Plugin', $text, $line, $msg));

If you don't get a result, deactivate your plugins and check which plugin causes the issues.

[fourroses666]

--screendump removed--

hmm, something is going wrong badly, I have no time to look any further on this moment, I will try to move to an other host.

(I think it's MM)

[Jako]

But that is a completely different code causing the error now.