I installed Wassup, but when I network activated it, the server began showing php deprecation warnings to users viewing any of the client sites (and the main site, and admins in the control panel).
It’s as if wp_debug_display were set to true in wp.config.php and error_reporting set to include e_notice instead of only e_error.
This was, obviously, unacceptable. I had to deactivate the plugin.
Why was it doing that, and is there any way to stop it other than deactivation?
Example of the errors:
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; wassupOptions has a deprecated constructor in wassup.class.php on line 38
Notice: The called constructor method for WP_Widget in A2A_SHARE_SAVE_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in functions.php on line 3721
Notice: The called constructor method for WP_Widget in evoFC_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in functions.php on line 3721
Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in functions.php on line 3845
Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘enqueue_admin’ not found or invalid function name in plugin.php on line 525
-
This reply was modified 7 years, 1 month ago by
Kaz Vorpal.
-
This reply was modified 7 years, 1 month ago by
Kaz Vorpal.
-
This reply was modified 7 years, 1 month ago by
Kaz Vorpal.