Apache Friends Support Forum

Hi all:

I'm running Xampp 1.8.0 on OpenSuse 12.1, I'm running a php app on my server (activecollab), anyways the app has a lot of strict standards warnings, I tried to disable them by changing error_reporting on my php.ini from:

Code: Select all

error_reporting = E_ALL

to:

Code: Select all

error_reporting = E_ALL & ~E_STRICT

but that didn't help, the warnings were still showing, then I tried:

Code: Select all

error_reporting = E_ERROR
display_errors = Off

And yet the warnings were still shown, I even tried leaving error_reporting without a value and the warnings were still shown, they don't actually affect the app but my users get scared every time they see them.

Now before you ask, I did check on my phpinfo the path to my php.ini and I checked every time I changed the error_reporting level and the changes were sticking, I just don't know what to do now except downgrading Xampp to 1.7.7. Can anyone help me with this one??

I forgot to mention, the warnings weren't displayed on Xampp 1.7.7.

1. Warnings probably due to newly deprecated functions. They are WARNINGS, not errors after all.

try this setting:
E_ALL & ~E_DEPRECATED

2. Best place for answers on this issue is the Developer's support. you may need an upgrade of patch. OR Fix the code.

3.

but my users get scared every time they see them.

This is precisely why we don't recommend XAMPP/LAMPP for production environments.

Good Luck


yslcf

I'm having the exact same issue. I upgraded to 1.8.0 and suddenly strict warnings are always displaying regardless of setting them to off with error reporting. I did not have this issue on 1.7.7. I've tried everything to disable the strict warnings, but they won't go away. I've tried the below.

E_ALL & ~E_STRICT
E_ALL & ~E_DEPRECATED & ~E_STRICT
E_ALL & ~E_DEPRECATED

None of the above worked.

Krileon -

Are you on WIndows or Linux -

If you are on Linux with LAMPP 1.8.0 please change your profile

If you are on Windows, post your own Message on the XAMPP for Windows board.

These are separate compiles, so it 'could be a Linux only bug on XAMPP, or a Windows only Bug on XAMPP, or a PHP bug on all platforms'

OR it could be there is a change the the error reporting syntax for PHP 5.4 -- XAMPP 1.7.7 was PHP 5.3.8

Good Luck

I'm on Windows, but was posting here because the issue appears present in both.

I however figured out what the cause was. It's due to E_STRICT being merged into E_ALL in PHP 5.4. In Joomla if debug mode is enabled it'll set the error reporting to E_ALL and thus you'll get strict warnings.

If anyone has any suggestion on how to stop PHP.ini error_reporting from being overwritten by error_reporting function then am all ears. I tried disable functions, but was just slammed with a bunch of security warnings instead.

I've just went back to previous Xampp release as Joomla isn't PHP 5.4 ready yet it seams.

To both posters -

This is NOT related to your problems - However, it would have value to me, who works on several Open Source projects...

I'd be very curious to know why you upgraded as you were both on a very recent release. You can PM me if you would prefer. It would help me adjust my thoughts on beta-testings and upgrades.

Thank you very much

Basically just to test out PHP 5.4 on my projects.

@ Krileon -

Thanks for posting your findings, I'm slammed building a website for another Open Source project. I would not have been able to get on this before late tonight. Altrea is probably headed for some rest by now, and we would have been some hours before having an answer. I suspected that might be the case, there are similar Apache issues as well. Two major upgrades in one release. I see I need to add to my stickies again

Thanks again

I updated because of both company policy and my desire to test PHP 5.4 features as well.

I'm going to test the issue on Win7/Ubuntu 12.10 and OpenSuse 12.1 tonight, will post my findings tomorrow.

One question I have is, can any application override the previously defined error_reporting variable??

There are different ways to override this value, yes.
php error_reporting can be setted with php configuration, Apache configuration, .htaccess files and the php function error_reporting().

Thanks for the info Altrea, I just finished checking and the warnings appear on all 3 platforms (Win7/Ubuntu 12.04/OpenSuse 12.1), my problem was that the app was overriding the servers error_reporting configuration with it's own, maybe Krileon's problem's the same.