philucky.com app.Enjoy Free 888+200 Daily Legal Bonus

Bugs

mihdan — Wed, 09 Mar 2016 14:42:01 +0000

1. E_STRICT Non-static method AECCore::can_edit() should not be called statically – /var/www/html/wp-content/plugins/wp-ajax-edit-comments/lib/class.filters.php:9

2. E_STRICT Non-static method AECCore::can_edit() should not be called statically – /var/www/html/wp-content/plugins/wp-ajax-edit-comments/lib/class.filters.php:35

3. E_STRICT Only variables should be assigned by reference – /var/www/html/wp-content/plugins/wp-ajax-edit-comments/lib/class.core.php:18

https://www.ads-software.com/plugins/wp-ajax-edit-comments/

E_STRICT Warning: Creating default object from empty value Line 214

redpixelstudios — Thu, 18 Sep 2014 14:34:37 +0000

Just wanted to pass along a warning that came up during development of a site using Swerve. The error seems to be resolved by declaring the $wp_query global in the swerve_redirect_action function. Of course this is not an issue that will affect most users since PHP error reporting is rarely set to trigger on E_STRICT level issues.

Thanks for your work on this useful plugin.

https://www.ads-software.com/plugins/swerve/

Optional error level to use with WP_DEBUG

ojrask — Thu, 29 Aug 2013 13:04:43 +0000

Hello.

tl;dr -> Allow PHP error reporting level (which WP_DEBUG would use) to be set in wp-config.php to suppress possible errors between wp-config.php and the after_setup_theme hook.

I have a feature request regarding WP_DEBUG and the level of errors that WordPress spits out when WP_DEBUG is enabled.

In newer PHP version E_STRICT has been merged with E_ALL, so WordPress begins to report E_STRICT errors too. During theme development this is great … until you install a 3rd party plugin with a bit outdated code.

The E_STRICT reports appear usually on each and every page, because plugins are not being loaded “according to strict standards”.

I’d rather keep theme related and plugin related strict standards notices separated. Because plugins are seemingly loaded before the after_setup_theme (the first hook available to hook into from functions.php) I cannot suppress plugin related errors in theme code (I tried various ways of setting the error_reporting value).

Setting the error level in wp-config.php does not work either, as WordPress resets the value in wp-includes/load.php. When WP gets to after_setup_theme the system has already possibly complained about numerous errors when loading non-theme specific contents.

Could an additional PHP constant be created to be used with WP_DEBUG (e.g. WP_DEBUG_LEVEL or similar). This constant would be optional and would default to whatever the current WP version uses. It should be able to be changed in wp-config.php.

Thanks.

EDIT: I know how to use mu-plugins, but I personally think this feature could be useful a core addition.

millions of error lines in log

rykios — Thu, 21 Oct 2010 11:02:54 +0000

Hello guys,

recently installed wordpress 301, seen today in error log million of lines of this type:

[21-Oct-2010 10:04:45] PHP Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /home/radicio/public_html/wp-includes/classes.php on line 724
[21-Oct-2010 10:04:45] PHP Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /home/radicio/public_html/wp-includes/classes.php on line 724
[21-Oct-2010 10:04:45] PHP Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /home/radicio/public_html/wp-includes/classes.php on line 724
[21-Oct-2010 10:04:45] PHP Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /home/radicio/public_html/wp-includes/classes.php on line 724
[21-Oct-2010 10:04:45] PHP Strict Standards: is_a(): Deprecated. Please use the instanceof operator in /home/radicio/public_html/wp-includes/classes.php on line 724

Any ideas? How to prevent all those errors from happening :S

E_STRICT PHP5 OOP

Covi — Fri, 12 Feb 2010 10:52:33 +0000

When will fix strict type errors as is_a(), etc…?
So… when we have php5 OOP?