Ilari Arovuo

This is nothing new – the plugin has had these issues for years! – and it seems developers are clueless why it’s happening.

A) The Plugin seems to be quite buggy, it leaves garbage after deactivation and deletion.
– Left over files, database rows and transients.
– If you can’t make working plugin, can you at least clean after yourself?

B) This plugin also utilizes transients incorrectly, expecting them to stay in the system.
– The developer did NOT read this: https://developer.wordpress.org/apis/transients/

“Transients should be used to store any data that is EXPECTED TO EXPIRE, or which can expire at any time. Transients should also never be assumed to be in the database, since they may not be stored there at all. (MEMCACHE anyone?) It is possible for the transient to NOT be available before the expiration time. Much like what is done with caching, your code should have a fall back method to re-generate the data if the transient is not available.”

Not only does this plugin use transients incorrectly, but it also relies on transient data for the connection to work, even though transients may disappear at any time. Additionally, some transients are set as persistent and are not deleted when the plugin is removed. Not defining expiry for transient, does not mean it will stay available. Transients WILL disappear!

After plugin deletion, it also leaves multiple entries in the wp_options table where option_name contains “mwp”. These leftover entries remain there even after reinstalling the plugin, leaving you stuck with the same connection issues.

I just used following process for ~20 disconnected websites, and it seems to restore the connection.

Shit ton of unnecessary work due developers, who are not bothering to read the WP Developer Resources and Handbook. … and yet we have to pay monthly fees for this CRAP.

Here’s how:
0) Take full filesystem and DB backup.

1) Deactivate and delete the plugin – if you can find it in the plugins list.
(Check your white label settings in the MWP dashboard.)

2) Go to wp-content/mu-plugins – delete 0-worker.php, if present.

3) Go to wp-content/plugins – delete worker folder, if present.

4) Go to the database – search options table for “mwp” and delete all items, where option_name has mwp in it. Including this one: _site_transient_mwp_sessions
Make sure you do not delete rows, where mwp is not in the option_name.
– DELETE FROM wp_options WHERE option_name LIKE ‘%mwp%’;

5) Reinstall the plugin – Activate it.

6) Navigate here: https://<your-website-url>/wp-admin/plugins.php?mwp_force_key_refresh=1

7) Copy the connection key and paste it to the MWP Dashboard

If it still does not work, you can try this: (replace key with given one)
INSERT INTO wp_options (option_name, option_value, autoload)
VALUES (‘mwp_communication_key’, ‘12345678-1234-1234-1234-123456789012’, ‘yes’)
ON DUPLICATE KEY UPDATE option_value = ‘12345678-1234-1234-1234-123456789012’;

1. Deactivate and delete the plugin
2. Delete option_name _site_transient_mwp_sessions from options table in database
3. Reinstall plugin and reconnect

Plugin seems to have a bug (for very long time) – it uses transients for persistent session/connection data – but, does not consider memcache which could be enabled and disabled at any point of time.

Very poor choice by developer using transient for persistent data storage, and not consider memcache while playing with transients. Back to school boys!