Hate to break the news . . .

There’s a problem in the release files on the download page. in manager/includes/document.parser.class.inc.php there’s a ton of commented code that isn’t commented out correctly, which causes the entire MODx program to launch into this error when it loads (after it installs):

Parse error: parse error, unexpected T_CLASS in /home/public_html/manager/includes/document.parser.class.inc.php on line 1

Just thought you all would want to know.

-Andy

Actually it’s a problem with your FTP client stripping line endings from the file. See this thread:

http://modxcms.com/forums/index.php/topic,4008.0.html

Who would have thought?

Wow . . .

Go figure . . .

Actually, I may be unjustly maligning your FTP client. This may have something to do with the fact that the developers all work on different machines, some Windows, some Mac, some *nix such as Linux. Each of these systems natively use different ways of indicating end-of-line, some use /n, some use /r and some use /r/n. It may be that certain hosts use an OS that doesn’t recognize whichever line ending was used. It may be space aliens. Whatever is doing it, the entire file becomes one really long line. Very annoying, to say the least. I find that usually if I have my programming editor convert a file to Unix line endings, then upload it, I have no problems with it. It’s become a habit now, whenever I’m dealing with a new .js file, or a new css file. I’ve never had this happen with any of the core files, however.