Re: parsing "problem" with 4.0.5

"Liz" <liz@xcalibur.co.uk> wrote: >> With 4.0.4pl1 and earlier, this did not occur, but with 4.0.5, there >> are some files on our server that are not getting parsed as php, and >> just showing up as the code itself. The problem files are a mess, but >> I only mention them since they got parsed before. They are php files >> that the designers here have created in HomeSite and saved as PC >> format, so they are basically 1 long line when I open them in vi, and >> have ^M's everywhere. If they pull them back into HomeSite and save >> as UNIX format and upload, no problem. What changed in PHP that would >> make this difference. I would just tell them to do this with all the >> problem ones, but there are a lot. > It shouldnt show as 1 long line with ^M every so often, if its in PC format it > should just have ^M at the end of every line. It is indeed one long line with lots of ^M's. There are simply supposed to be a lot of blank lines. > Are you sure that no one has accidentally uploaded them since you changed to > 4.0.5? I know my linux box has no problem with PC formatted PHP pages. Hence > I ask.. Yes. I am actually running 4.0.3pl1 or 4.0.4pl1 again for the site, and 4.0.5 on another port, and loading the same file with one parses it correctly and the other shows the code itself. -Ken