Here’s what I ended up doing. Would appreciate some feedback on this. Also, curious as to why you guys are running your function wpas_single_activate() on EVERY blog (network site) within a multisite network, hooked to the wpmu_new_blog action? If the administrator of the network did not choose to network-enable your plugin, shouldn’t you not be touching anything related to the network sites?
// turn of the action of Awesome Support adding itself to every network site
function chrisv2_wpas_no_network_sites() {
remove_action( 'wpmu_new_blog', 'wpas_activate_new_site', 10 );
}
add_action( 'wp_login', 'chrisv2_wpas_no_network_sites', 99 );
With this, now PaidMembershipsPro works correctly again…but it feels “weird” to me that I had to do this…am I missing some setting somewhere, where your plugin will not attempt to run an install routine on network sites?
Disappointing that nobody could bother to reply to this.
Hey Chris,
Sorry for not replying earlier. What you’re saying seems correct to me. MS compatibility is something that has been looked into in the early days but we decided that there was no value at the time to support MS in a specific way.
The code you’re pointing at does, indeed, look unnecessary. I have opened a new issue about it and we will look into it asap: https://github.com/Awesome-Support/Awesome-Support/issues/371
