Multi NETWORK Support

At present, the way Wordfence stores it’s licence key in a non standard table called: wp_wfConfig. This table also includes the majority of the configuration for Wordfence.

Within a Multi-NETWORK environment this causes problems primarily because when Wordfence is network activated within more than one network at at time, it finds the same product key. It therefore believes (and quite rightly) that the API key is being used more than once.

Let me explain for those who are confused. In a Multi-NETWORK setup, all networks share the same users, database, filesystems and server. If I open the wp_site table within our database there are three entries, where in most cases there will only ever be one. This means that within our installation, there are THREE network Admin dashboards within the same physical installation of WordPress.

FOR THIS TO WORK – you either need to allow the use of a single API key for the entire installation OR base the API key check on something else such as a uniquely generated ID number OR you need to store the API key database entry inside the Blog ID attached to the Network Admin (In our case it would be wp_options [blog ID 1] AND wp_225_options and wp_235_options), OR Wordfence needs to be able to differentiate and store separate API Keys for each network in some other way (by perhaps serialising the API Key with network ID numbers from the wp_site table.).

Until one of those options are met, we are not able to enable premium features on ANY of the sites within our installation.

Wordpress Multi Network features are described by one of the WordPress developers here: https://wordpress.tv/2014/07/26/john-james-jacoby-multisite-and-multi-network/

I hope you implement this change. I don’t believe the changes to your plugin required to make this work to be that complex, I have given multiple options on how to do it I believe you could implement this quite quickly.