Carl Hartung wrote:

On Thu December 13 2007 01:58:28 pm Cristian Rodríguez wrote:

...

Those warnings have probably always existed, but you altered the error reporting level and they are now seen, that 's the only thing that can be deduced with such a poorly described problem.

But this 10.3 installation didn't exist yesterday! And I haven't modified anything... just toggled some GUI switches in YaST. ;-)

The only thing I've done differently this time is use rsync to transfer my files.

As far as being "poorly described" what are you looking for? These pages parsed and displayed properly yesterday under 10.2. They are now not parsing or displaying correctly in this fresh 10.3 installation and the only clues I have are the error messages I posted.

regards,

Carl

Carl, make sure you are using the php.ini file you think you are using.... I can't remember the version, but at one point the php.ini location changes from /etc/php.ini to /etc/php5/apache2/php.ini. You also might want to check /etc/apache2/conf.d/php.conf to see if there are any path or config problems. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

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

On Thu December 13 2007 03:13:12 pm Cristian Rodríguez wrote:

Sloan escribió:

...

I'm guessing here - the default php configuration seems to have gotten stricter with each suse release,

Yes.

...

so they might be getting bitten by e.g. the requirement of

None of those you mentioned are SUSE specific configuration changes, those comes from upstream, we currently try to deviate as litle as possible from the upstream "reccommended" default configuration.

The culprit is in /etc/php5/apache2/php.ini:

; Allow the

In 10.2 it was set to 'short_open_tag = On' So, half of the projects and frameworks I've been studying fail this 'test'. Interesting! At least my broken pages were easily repaired, so this is not too big a deal. Thanks, everybody, for your kind responses. On another note... I think this is the fastest SuSE/openSUSE upgrade/migration I've ever accomplished. I had 10.2 highly customized and was able to replicate all that hard work which had been stretched out over months in less than a day. And it is all just working now. Amazing! Great job, Novell/openSUSE team! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org