How to eliminate php5 Strict standards errors?

Question

After upgrading my PHP to 5.4.3 (WAMP server 2.2), my web app made in CakePHP 1.3, is showing the following errors in my index:

Strict standards: Redefining already defined constructor for class Object in C:...\cake\cake\libs\object.php on line 63

Strict standards: Non-static method Configure::getInstance() should not be called statically in C:...\cake\cake\bootstrap.php on line 49

I've found that some people solve this problem by setting the error_reporting in php.ini to E_ALL & ~E_STRICT.

I did that in both php.ini files (C:\wamp\bin\php\php5.4.3 and C:\wamp\bin\apache\apache2.4.2\bin) present on my computer but it didn't solve the problem.

I also tried to put php_value error_reporting 6143 in C:...\cake.htaccess but without success.

Does anybody know how can I solve this? I can't upgrade my CakePHP because of firebird.

did you also restart apache then? also - usually for WAMP you can navigate to the right php.ini by clicking the icon and selecting PHP=>php.ini — mark, Sep 01 '12 at 15:40
In my case the solution for these problems is to upgrade CakePHP which I can't do since CakePHP 2.x do not support firebird. I've printed the phpinfo() and it show that my php.ini file is located at C:\wamp\bin\apache\apache2.4.2\bin. I did restart apache. And no, the php.ini file opened in the wamp menu is not the correct one. — qxlab, Sep 01 '12 at 16:26
Running PHP 7 on IIS Win10 for development only Modifying the php.ini file solve it for me. error_reporting = E_ALL & ~E_STRICT & ~E_DEPRECATED — Nick, Feb 03 '18 at 20:24

score 23 · Accepted Answer · edited Nov 27 '13 at 10:35

23

One of the changes in php 5.4 is that E_STRICT is now part of E_ALL

So, in your /cake/bootstrap.php you could remove the E_STRICT from your error reporting:

error_reporting(E_ALL ^ E_STRICT);

and be compatible again with before 5.4 versions.

edited Nov 27 '13 at 10:35

Jpsy

20,077
7
118
115

answered Sep 01 '12 at 15:50

JvdBerg

21,777
8
38
55

6

Thank you!! I put "error_reporting(E_ALL & ~E_STRICT & ~E_DEPRECATED);" in my C:\...\cake\cake\bootstrap.php file and that solve the problem. – qxlab Sep 01 '12 at 16:36
1

after using this one `error_reporting(E_ALL & ~E_STRICT & ~E_DEPRECATED);`my views has gone... any help? – MuntingInsekto May 14 '13 at 03:04
I applied same thing in bootstrap.php, but no change in Strict Standard. – Amit Jha Jun 05 '14 at 09:56
It's because it gets overwritten by your `core.php` file (`Configure::write('Error'...)`). See the answer further down. – Claudio Bredfeldt Jul 24 '14 at 07:39

score 14 · Answer 2 · answered Apr 18 '13 at 22:28

14

Instead of modifying the cake core files, which sucks if you want to update your cake version, go into your Config/core.php file and look for the error handler configuration:

Configure::write('Error', array(
    'handler' => 'ErrorHandler::handleError',
    'level' => E_ALL & ~E_DEPRECATED,
    'trace' => true
));

and replace 'level' with this:

...
'level' => E_ALL & ~E_STRICT & ~E_DEPRECATED,
...

answered Apr 18 '13 at 22:28

Claudio Bredfeldt

1,423
16
27

1

This is the best option - my `error_reporting` in `bootstrap.php` was being overridden by these settings anyways. – jocull Jun 18 '14 at 17:30
For users of CakePHP, this is THE correct solution. Changing the PHP.INI file has NO effect since it gets overridden here. – UncaAlby Oct 17 '17 at 14:51

score 9 · Answer 3 · answered Mar 18 '13 at 16:21

9

Please replace

error_reporting = E_ALL

in your php.ini, with

error_reporting = E_ALL & ~E_STRICT

For me

error_reporting(E_ALL ^ E_STRICT);

which is shown in the accepted answer to this question did not work and gave an Infinite loop detected in JError error for my Joomla website.

answered Mar 18 '13 at 16:21

Ruut

1,091
1
16
29

As I stated in the comment in the correct answer, to solve my problem I used `error_reporting(E_ALL & ~E_STRICT & ~E_DEPRECATED);`, right now I don't remember why.. – qxlab Mar 29 '13 at 00:45

score 4 · Answer 4 · answered Jan 10 '14 at 18:09

4

You are using newer php version. in php 5.4, E_STRICT is part of E_ALL

in cake 1.3, open file /cake/bootstrap.php and change the error_reporting like this

error_reporting(E_ALL & ~E_STRICT & ~E_DEPRECATED);

answered Jan 10 '14 at 18:09

GIPSSTAR

2,050
1
25
20

score 1 · Answer 5 · answered Jun 23 '15 at 19:08

If you're fighting with PHP Strict warnings in cake console output, take a look into your app/config/core.php.

In CakePhp 1.3 error_reporting(...) is overwritten by the 'log' option, so ensure you exclude E_STRICT here:

/**
 * CakePHP Log Level:
 *
 * In case of Production Mode CakePHP gives you the possibility to continue logging errors.
 *
 * The following parameters can be used:
 *  Boolean: Set true/false to activate/deactivate logging
 *    Configure::write('log', true);
 *
 *  Integer: Use built-in PHP constants to set the error level (see error_reporting)
 *    Configure::write('log', E_ERROR | E_WARNING);
 *    Configure::write('log', E_ALL ^ E_NOTICE);
 */
Configure::write('log', E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE);

cori · Answer 6 · 2012-09-01T15:53:14.047

0

Make sure you've updated the correct php.ini file - if you create a php file in your root directory with the following code

<?php

phpinfo();

?>

and load it in your web browser it will tell you which ini file is being used, in case you missed one.

It's also possible that an htaccess file is setting that value via the php_flag error_reporting value, which can also be set per directory.

edited Sep 01 '12 at 15:53

answered Sep 01 '12 at 15:42

cori

8,666
7
45
81

Thank you for the answer, the phpinfo() shows that I'm changing the correct php.ini file. I didn't understand your comment about the htaccess... should I try something? – qxlab Sep 01 '12 at 16:29

KingRider · Answer 7 · 2015-07-27T18:58:51.950

0

File bootstrap.php from folder (root)cake

if (!defined('E_ALL')) {
    define('E_ALL', 8192);
}

File debugger.php from folder (root)cake\libs

error_reporting(E_ALL ^ ~E_STRICT ^ ~E_DEPRECATED);

edited Jul 27 '15 at 18:58

answered Jul 27 '15 at 18:37

KingRider

2,140
25
23

How to eliminate php5 Strict standards errors?

7 Answers7

Linked