Wassup with Multisite?

Yes.
Just install Wassup plugin as super_admin (network admin), network activate it, then go to Wassup =>Options under the main site and make sure that “Enable statistics recording for network” is checked. You can change Wassup settings here to set default values for all sites in the network as well.

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, 2 months ago by Kaz Vorpal.
• This reply was modified 7 years, 2 months ago by Kaz Vorpal.
• This reply was modified 7 years, 2 months ago by Kaz Vorpal.

If I’m going to use this product for my client’s thousands of subdirectory customers, I need the fact that it’s flipping on the warnings and notices flag addressed.

Or Am I expected to go through the plugin’s code and find it for myself?

Sorry that you had trouble with Wassup and thank you for your detailed error report.

We are in process of updating Wassup code to be PHP7 compatible and that will eliminate those “deprecated” warnings. However, the warnings should not have displayed to users at all. That is a different bug that I will look into immediately.

I may have found the problem, or at least a kludge to prevent it:

I had wp_debug and wp_debug_log set to true, but wp_debug_display set to false, so that the debugging strings went to the log file, not to user’s browser.

Turning off wp_debug and wp_debug_log stopped the stupid warnings and notices that were being shown to the users via browser when Wassup was enabled.

But I don’t know why it was doing that, in the first place. If I have wp_debug_display set to false, it should never show debug strings to the user. I prefer to have the debug set to on (but only to a logfile) all the time.

To be clear, my issue wasn’t with the code being deprecated, just with the notices being shown when I had them set to not be.

• This reply was modified 7 years, 1 month ago by Kaz Vorpal.
• This reply was modified 7 years, 1 month ago by Kaz Vorpal.

Okay, I have been unable to leave Wassup running on this 8,000 member multisite install, because it singlehandedly drags the server to a near-halt.

Once I activate network tracking, pages start loading visibly more slowly…within a short time, most page load requests time out entirely. Occasionally they’ll still load, but after a lot of lag, sometimes as much as a minute or two.

Do you have any idea what could cause that?

Should I start a new thread?