If you are logging errors about Undefined Indexes & variables, that definitely has something to do with your error_reporting level. My 10.3 defaulted to E_ALL, so I changed it to my usual operating level, "E_ALL & ~E_NOTICE | E_STRICT"
From php.ini:
E_NOTICE - run-time notices (these are warnings which often result ; from a bug in your code, but it's possible that it was ; intentional (e.g., using an *uninitialized variable* and ; relying on the fact it's automatically initialized to an ; empty string) --Peter Keens Sloan wrote:
Carl Hartung wrote:
Hi All,
I've successfully migrated into 10.3 from 10.2 with one small problem: *.php files aren't parsing correctly and it seems the problem is limited to user public_html directories. They're definitely parsing but none of the includes are displaying and apache2 is logging lots of "Undefined index", "Undefined property" and "Undefined variable" errors. Anybody have an idea where to look?
I'm guessing here - the default php configuration seems to have gotten stricter with each suse release, so they might be getting bitten by e.g. the requirement of
Just a shot in the dark, maybe there's something helpful here.
Joe
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org