PhpStorm - How to detect PHP error "Non-static method should not be called statically"?

Question

With PHP, static method can be used in both static method and non-static method, and non-static method can only used in non-static method. That's why calling a dynamic method statically generates the E_STRICT error.

For example:

<?php

class Example
{
    public function foo() {
        return "Foo";
    }

    public static function bar() {
        return "Bar";
    }
}

$ex = new Example();

// Non-static call
echo $ex->bar();

// Static call on a non-static method
// PHP Error "Strict standards: Non-static method should not be called statically"
// ERROR NOT DETECTED BY PHPSTORM!
echo Example::foo();

The last line will generated this PHP error (it's logic):

I am currently working on a large PHP application that calls, in some PHP files, non-static methods statically. It was not a problem with an very old version of PHP but we have decided to migrate to the latest PHP version.

Manually check all the project files to identify this bad syntax will be too long (+ 1000 files)!

The built-in code inspection features of PhpStorm doesn't detect this type of error within the analyzed source code. Why? Should I configure something? How?

Below, my PHP code inspection configuration in PhpStorm:

Thanks!

Works fine: postimg.org/image/y82q2zzuj 1) Try Code | Inspect Code... on this file; 2) or even File | Invalidate Caches... and restart IDE. — LazyOne
– LazyOne, Commented Nov 27, 2015 at 10:11
To run this inspection only -- use Code | Run Inspection by Name... (it's faster that doing full Inspect Code for each file). — LazyOne
– LazyOne, Commented Nov 27, 2015 at 10:14
I think that Invalidate Caches and a full restart of PhpStorm did the trick. Inspection of this specific error seems to be buggy, I don't understand why (totally OK with other PHP errors/warnings). @LazyOne : in any case, thanks! s28.postimg.org/gr2aoquyl/phpstorm_php_inspection_3.png — Guicara
– Guicara, Commented Nov 27, 2015 at 10:19

LazyOne · Accepted Answer · 2015-11-27 10:31:57Z

5

That inspection works fine here (proof).

Please try Code | Inspect Code... on this file -- it will force re-analysing of this file from scratch. Any better?
If nothing -- please do File | Invalidate Caches... and restart IDE

P.S.
If you are interested of running this inspection only on whole project -- use Code | Run Inspection by Name... -- it's much faster that doing full Inspect Code for each file.

answered Nov 27, 2015 at 10:31

LazyOne

167k49 gold badges420 silver badges422 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Guicara Over a year ago

I think that Invalidate Caches and a full restart of PhpStorm did the trick. Inspection of this specific error seems to be buggy, I don't understand why (totally OK with other PHP errors/warnings). @LazyOne : in any case, thanks! s28.postimg.org/gr2aoquyl/phpstorm_php_inspection_3.png

Alex Blex · Accepted Answer · 2015-11-27 10:22:24Z

1

Static code analysis may hint some potential errors. It never guarantees there are no errors, and one really shouldn't rely on it.

As a practical advice, you can search for all static calls with something like

grep -roh "\w\+::.\+\?("

and analyse the list yourself.

answered Nov 27, 2015 at 10:22

Alex Blex

37.3k7 gold badges53 silver badges87 bronze badges

Comments

Sharmila Juliet · Accepted Answer · 2016-01-07 11:09:37Z

0

Change the error reporting in your php.ini file

error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING & ~E_STRICT & ~E_DEPRECATED

answered Jan 7, 2016 at 11:09

Sharmila Juliet

331 gold badge1 silver badge3 bronze badges

Collectives™ on Stack Overflow

PhpStorm - How to detect PHP error "Non-static method should not be called statically"?

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related