>> Errors With QuickStatus

I get errors I don't understand with QuickStatus, how can I do to suppress theses errors ? Thank You Very Much
// ACCES IS GRANTED
Strict Standards: Non-static method Wdqs_Installer::check() should not be called statically in /var/www/vhosts/comme1marque.com/httpdocs/wp-content/plugins/quick-status/quick-status.php on line 98

Strict Standards: Redefining already defined constructor for class Wdqs_PublicPages in /var/www/vhosts/comme1marque.com/httpdocs/wp-content/plugins/quick-status/lib/class_wdqs_public_pages.php on line 12

Strict Standards: Non-static method Wdqs_PublicPages::serve() should not be called statically in /var/www/vhosts/comme1marque.com/httpdocs/wp-content/plugins/quick-status/quick-status.php on line 125

  • Predrag Dubajic
    • Support

    Hey Laurent_C,

    Hope you're doing well today :slight_smile:

    I had a look at your site but couldn't see these notices, can you tell me where are you seeing them?

    Note that these are just notices and it shouldn't affect your site functionality in any way, you should set wp_debug to false in your wp-config.php to hide them from your site.

    When I replicate this I will also report it for our developers so they can check it out.

    Best regards,
    Predrag

  • Adam Czajczyk
    • Support Gorilla

    Hello Laurent_C!

    As my colleague Predrag already stated it's a notice and not an actual error. It's meant for the developers to help them optimize the code but whether it's shown or not depends mostly on PHP configuration.

    The main reason for this notice is to help developer stick to strict PHP standards so "fixing" it would require refactoring plugin's PHP code . However, in 99.99% of cases it would mean maintaining a separate version of a plugin for each and every PHP version available which is not quite possible.

    Until PHP 5.4 such a message rarely showed up at all. The "error_reporting" configuration option of PHP must include "E_STRICT" option and in "pre PHP 5.4 era" it was not a default setting though some hosting providers/server admins were setting it.

    Since PHP 5.4 "E_STRICT" reporting is enabled by default and that's why this error comes up.

    The conclusion is that it is absolutely harmless and doesn't affect the script/plugin. Switching it off is the simplest and good enough solution. That said, switching "WP_DEBUG" off would do the trick but if you'd like to get rid of such notices "for good" you would need to change PHP configuration. If your hosting provider allows custom PHP configuration, here's a guide on how to do this:

    http://www.inmotionhosting.com/support/website/php/strict-standards-fix

    Best regards,
    Adam

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.