Originally posted by philipolson
Look for a missing }, or quote. Parse errors are always syntax errors.
Yep, that's how I see it. Problem was I'd pored over the code looking for missing quotes, brackets, misspelled functions, mismatched variable names, etc., etc., for hours. I removed all included files and pasted their contents within the script so I could see the whole blasted thing, and I commented every closing bracket with a reference to its opening....etc., etc.,
I then actually read more of "file_get_contents" in the manual than I needed to...and discovered that I was using a version of php (4.2x) built prior to the inclusion of this function....
So, I guess the question was...would calling "file_get_contents" on a script on php 4.2x cause a syntax (parse) error, since "file_get_contents" was only introduced in v4.3.0 ??
Thanks....