Strict Standards Errors

  • I’m running PHP 5.4.10 and WordPress 3.8.2 with debug mode turned on. GD Press Tools is creating quite a lot of errors, including:

    Strict Standards: Non-static method gdFunctionsGDPT::size_format() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 80

    Strict Standards: Only variables should be passed by reference in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 187

    Strict Standards: Non-static method gdFunctionsGDPT::size_format() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 561

    Strict Standards: Non-static method gdFunctionsGDPT::size_format() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 515

    Strict Standards: Non-static method GDPTDB::insert_posts_views() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 703

    Strict Standards: Non-static method GDPTDB::insert_users_tracking() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 713

    Strict Standards: Non-static method gdFunctionsGDPT::size_format() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 80

    Strict Standards: Only variables should be passed by reference in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 187

    Strict Standards: Non-static method gdFunctionsGDPT::size_format() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 561

    Strict Standards: Non-static method gdFunctionsGDPT::size_format() should not be called statically, assuming $this from incompatible context in /Applications/MAMP/htdocs/HabitFree/wp-content/plugins/gd-press-tools/gd-press-tools.php on line 599

    https://www.ads-software.com/plugins/gd-press-tools/

Viewing 3 replies - 1 through 3 (of 3 total)

  • Your not alone. I have about 40 WordPress sites I am looking after and found that as of 3.8.2 many of them are a lot of errors around the strict standards issue and some are also generating core dumps Linux which results in huge files rapidly filling the available storage.

    After a bit of diagnostic work we found the issue to be with plugins that are not written to be strictly compliant with PHP 5.4 (which we are running on the server). What is interesting is that this has always been the case, but in previous versions of WordPress it has not caused any visible hiccups. It seems that 3.8.2 is much more rigorous in its parsing of the plugin code and is intolerant of anything that is not 100% compatible with the server.

    We are trying to downgrade some of the most problematic sites to PHP5.3 and will keep watch on these for the core dumping and let you know the outcome.

    It’s be nice to think that this will be resolved in 3.9 due out this week.

    Is anyone else experiencing issues with WP 3.8.2 since upgrading?

    Update:
    It seems that either of the following two steps temporarily the issues.

    • Option 1 – Downgrade your server to an earlier release of PHP which is fully compliant with both wordpress and the plugins
    • Option 2. Downgrade WordPress to 3.8.1

    Neither of these are really acceptable in the long term, but for anyone experiencing this issue at present they may help.

    Thread Starter Narthur

    (@narthur)

    Thank you for researching this, rethinkmarketing!

    Until the plugin author updates the extension, I’ve gone to using the WP Error Fix plugin to view errors in place of displaying errors on the website. (Note that you’ll have to edit wp-config.php to turn off error display separately—this plugin won’t do it for you, as far as I know.) Anyway, works like a charm. Lets me filter errors by source so I can keep working on my own plugins even when other plugins are generating loads of errors.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Strict Standards Errors’ is closed to new replies.