Problem (searched but cant find)

Ah, I thought that error looked familiar; this jogs my memory! I’ve had it before; sometimes my ftp client program (or something) strips all line endings from the file, which of course totally trashes the file since now all comments (//) are part of the single line the file has turned into, making the entire file following the first comment one huge comment!

You’ll need to go to your original unizpped package and re-upload the offending file. I find that I often have this problem with files that were created on a Windows machine, and most frequently .js and .css files; if I take the file in its original (correct) state and convert it to Unix line endings then I have no trouble with it.

Perfect. Thank you.
Had to install a different ftp client and uploaded that file and now its great.

Thanks again!!

*off to tinker*...

Quote from: parkourdan at Apr 18, 2006, 06:06 AM

Perfect. Thank you.
Had to install a different ftp client and uploaded that file and now its great.

Thanks again!!

*off to tinker*...

I’m having the exact same problem. I uploaded the MODx files using both WS_FTP Professional 2006 and FileZilla, and I got the error in both cases. What FTP client did you use?

Thanks
Ron

You can also use a file conversion utility (my programmer’s editor has the feature) to convert the offending file to use Unix line endings. At least this seems to solve the problem in my case .

Quote from: sottwell at Apr 20, 2006, 09:18 PM

You can also use a file conversion utility (my programmer’s editor has the feature) to convert the offending file to use Unix line endings. At least this seems to solve the problem in my case .

Saving the manager/includes/document.parser.class.inc.php file to use UNIX line endings and uploading it again did the trick. Everything’s working fine now. It might be an idea to include this file with UNIX line endings in the installation package. This might prevent installation issues.

Ron

Er, maybe not everything is working as it should. I can log in and the demo site comes up, but I’m getting lots of "Stack overflow at line: 511" errors. I have no idea what file this is referring to. Very frustrating...

UPDATE: False alarm, I guess. For some reason, after I rebooted, no more error messages. Everything seems OK now. I’ll play around with MODx. Looks very promising. I was initially looking at Etomite 0.6.1, but MODx seems better.

UPDATE 2: Nope, it’s back. The site and the admin stuff work, but I’m seeing popup windows with "Stack overflow at line: 511" error messages. I can click the OK button to continue with whatever I was doing.

UPDATE 3: It doesn’t seem to be related to MODx. I *seem* to have narrowed it down to Ad Muncher (which kind of suprises me as this little gem has never given me trouble before). If I turn it off, the error message *seems* to go away.

Ron

Just to let you guys know that i am also having this problem as well (MODx-091a) - its quite strange. Ive uploaded it with 2 different clients (FireFTP Firefox FTP Extension & CuteFTP 6 Pro) both with the same result



Ive never had this problem with previous versions.

I inspected the file after transfer and its all on 1 line as previously mentioned. I also checked the file from the archive file to check it wasnt on one line and it wasnt. I checked some other files on the server and they uploaded fine its just this 1 file which is uploading in a strange manner? Is there something in this 1 file that is causing the file’s line breaks to be stripped?

[UPDATE]
I forced the FTP Client to upload the document.parser.class.inc.php file in Binary Mode (instead of auto or ASCII) and it seems to have worked.

Ritchie.