Title: Problems with multisite
Last modified: August 21, 2016

---

# Problems with multisite

 *  Resolved [gtrout](https://wordpress.org/support/users/gtrout/)
 * (@gtrout)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/problems-with-multisite-1/)
 * I converted an existing large site with over 1000 user subscriptions to multisite.
   Afterward, users noted that their subscription preferences had all gone blank.
   I was able to solve the problem by changing the wpmu check on line 1620 of class-
   s2-core.php:
 * I replaced this:
 *     ```
       // Is this WordPressMU or not?
       		if ( isset($wpmu_version) || strpos($wp_version, 'wordpress-mu') ) {
       			$this->s2_mu = true;
       		}
       		if ( function_exists('is_multisite') && is_multisite() ) {
       			$this->s2_mu = true;
       		}
       ```
   
 * with this:
 *     ```
       if (is_main_site()) {
       			$this->s2_mu = false;
       		}else{
       			$this->s2_mu = true;
       		}
       ```
   
 * Can you suggest a better long term solution or add this check to the plugin so
   subscriptions don’t break on plugin upgrade? Thanks!
 * [https://wordpress.org/plugins/subscribe2/](https://wordpress.org/plugins/subscribe2/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Matt Robinson](https://wordpress.org/support/users/mattyrob/)
 * (@mattyrob)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/problems-with-multisite-1/#post-5014291)
 * [@gtrout](https://wordpress.org/support/users/gtrout/),
 * This issue has probably only arisen because you converted a single site WordPress
   install to a multisite one.
 * Also, the is_main_site() function returns true or a number which is the blog 
   id of the current site, so your fix probably won’t work reliably without further
   checks.
 * A longer term fix would be to import all of the users from the old blog to a 
   sub-blog on your multisite.
 *  Thread Starter [gtrout](https://wordpress.org/support/users/gtrout/)
 * (@gtrout)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/problems-with-multisite-1/#post-5014302)
 * Thanks for your quick reply!
 * I’m not sure I understand your advice. The “old blog” is still the main site.
   There are several sub-sites, each of which has a small subset of the main user
   base.
 * The problem seems to be that the original subscriptions are stored in wp_usermeta
   with the key `s2_subscribed` but that with multisite enabled you’re looking for
   a key with the wp_ prefix like `wp_s2_subscribed`.
 *  [Matt Robinson](https://wordpress.org/support/users/mattyrob/)
 * (@mattyrob)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/problems-with-multisite-1/#post-5014317)
 * [@gtrout](https://wordpress.org/support/users/gtrout/),
 * A fix may well be to user PHPMyAdmin or similar to rename all of the existing
   keys in the wp_usermeta table called `s2_subscribed` to `wp_s2_subscribed`. In
   multisite Subscribe2 needs to keep the settings for each blog separated. It does
   this by prefixing the database prefix for each subblog to the meta key name.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Problems with multisite’ is closed to new replies.

 * ![](https://ps.w.org/subscribe2/assets/icon-256x256.png?rev=2318630)
 * [Subscribe2 - Form, Email Subscribers & Newsletters](https://wordpress.org/plugins/subscribe2/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/subscribe2/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/subscribe2/)
 * [Active Topics](https://wordpress.org/support/plugin/subscribe2/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/subscribe2/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/subscribe2/reviews/)

## Tags

 * [multisite](https://wordpress.org/support/topic-tag/multisite/)

 * 3 replies
 * 2 participants
 * Last reply from: [Matt Robinson](https://wordpress.org/support/users/mattyrob/)
 * Last activity: [11 years, 11 months ago](https://wordpress.org/support/topic/problems-with-multisite-1/#post-5014317)
 * Status: resolved