Title: 4.7 Multi Network Issues
Last modified: December 12, 2016

---

# 4.7 Multi Network Issues

 *  [wadegibson](https://wordpress.org/support/users/wadegibson/)
 * (@wadegibson)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/)
 * I updated two separate multi-network installations to 4.7 last week. These are
   multi-network installs (not regular multisite). So far I have been able to isolate
   and reproduce these issues on both installations. Both installations are using
   the WP-Multi-Nework plugin, which only enables the multi-network user interface.
   I’ve removed that plugin altogether and can still replicate the issues below.
 * **1. Logout Issues** – on both installations, only the site(s) on the root/first
   network can successfully logout. For any other networks and their associated 
   sites, when we try to log out we get the WordPress Failure Notice prompt asking
   if we really want to log out. If we confirm we want to log out it will take us
   back to the login screen saying you are now logged out, but it never actually
   logs out of the user. Going back to /wp-admin takes you right in. I’ve replicated
   this in multiple browsers and using incognito mode as well.
 * **2. Password Protected Posts/Pages Broken** – similar to the issue above, password
   protected posts/pages only work on the site(s) associated with the root/first
   network on the install. All others won’t accept the password or allow access 
   to the protected content (no error, it just goes back to asking for password 
   again).
 * All plugins are up to date. I’ve already disabled and/or removed a whole herd
   of plugins and can still replicate both of these issues on a newly created test
   site with no plugins enabled. I’ve dug through my wp-config file and made sure
   all settings are correct. My .htaccess files were not edited recently and I’ve
   double checked those settings as well.
 * My gut thinks this might be an issue in the wp-login.php file, but I don’t know
   enough to troubleshoot within that file. Has anyone else had issues similar to
   these? Thanks in advance!

Viewing 15 replies - 1 through 15 (of 22 total)

1 [2](https://wordpress.org/support/topic/4-7-multi-network-issues/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/4-7-multi-network-issues/page/2/?output_format=md)

 *  [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * (@amibe)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8546234)
 * Without doing extensive troubleshooting I can report I’m not able to login on
   secondary networks or its sites. This may or may not be related to the same issue.
   My guess would be something to do with cookies?
 * I’ve also (theoretically) deleted the secondary network (and all its sites) and
   am now unable to create a new one.
 * I don’t have time (or necessity) to investigate further at this stage but happy
   to test changes that are suggested and report back.
 * Also, take a look at this which suggest there are known issues and there’s an
   update in progress that may resolve what’s being experienced: [https://wordpress.org/support/topic/latest-version-2-1-0-at-github/](https://wordpress.org/support/topic/latest-version-2-1-0-at-github/)
    -  This reply was modified 9 years, 3 months ago by [Amibe Websites](https://wordpress.org/support/users/amibe/).
      Reason: Added link to info on new plugin ver
 *  [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * (@amibe)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8546385)
 * As an aside I’ve logged the issue creating a new network here: [https://wordpress.org/support/topic/cannot-create-a-new-network/](https://wordpress.org/support/topic/cannot-create-a-new-network/)
 * Updating did not resolve that and until it is I cannot determine if updating 
   resolves the other issues experienced.
 *  [Justin Fletcher](https://wordpress.org/support/users/justinticktock/)
 * (@justinticktock)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8548428)
 * Just as a long shot … you have put a “Title” into the new settings for the new
   site?
 * It keeps getting me when I haven’t created a site for a while and rush to create
   one you actually need the Title otherwise it just doesn’t create the new Network.
 *  [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * (@amibe)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8550472)
 * [@justinticktock](https://wordpress.org/support/users/justinticktock/) Long shots
   are always worth checking out… and I was going to adamantly insist I was putting
   in a title… but you’re absolutely spot on!!! What I assumed (I know, I know) 
   was the (Network) Title is the Site Name… “Enter network title here” is the biggest
   text on the whole screen, can’t believe I missed it… guess I need to do some 
   UI changes to my admin template.
 * [@wadegibson](https://wordpress.org/support/users/wadegibson/) With 2.1.0 installed
   on WordPress 4.7 the following two lines in your wp-config may make the difference:
 *     ```
       define( 'WP_HOME',    '//' . $_SERVER['HTTP_HOST'] );
       define( 'WP_SITEURL', '//' . $_SERVER['HTTP_HOST'] );
       ```
   
 * Without them I experience the same as what you describe. With them both issues
   are resolved. Hope you come right…
    -  This reply was modified 9 years, 3 months ago by [Amibe Websites](https://wordpress.org/support/users/amibe/).
 *  Thread Starter [wadegibson](https://wordpress.org/support/users/wadegibson/)
 * (@wadegibson)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8552477)
 * [@amibe](https://wordpress.org/support/users/amibe/) That addition to wp-config.
   php did it! Everything is working great on both installs. Thank you, sir!
 *  [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * (@amibe)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8552540)
 * [@wadegibson](https://wordpress.org/support/users/wadegibson/) My pleasure, I’m
   so glad to hear.
 *  [Justin Fletcher](https://wordpress.org/support/users/justinticktock/)
 * (@justinticktock)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8594768)
 * [@amibe](https://wordpress.org/support/users/amibe/) I had the customizer failing
   with the authentication issue.. “_Your session has expired. Please log-in again._”
 * I haven’t found it necessary to add the ..
 *     ```
       define( 'WP_HOME',    '//' . $_SERVER['HTTP_HOST'] );
       define( 'WP_SITEURL', '//' . $_SERVER['HTTP_HOST'] );
       ```
   
 * in to wp-config before but adding it in fixed the customizer problem.
    thanks.
 *  [GlobalCultura.com](https://wordpress.org/support/users/globalcultura/)
 * (@globalcultura)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8605764)
 * [@amibe](https://wordpress.org/support/users/amibe/) I had same issue and, after
   adding the two lines to wp-config, all is working again.
 * Thank you!
 *  [fwdcar](https://wordpress.org/support/users/fwdcar/)
 * (@fwdcar)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8611141)
 * Hello wadegibson and other’s. I remember reading a while back about the security
   vulnerabilities with using HTTP_HOST. A quick search came up with this from the
   codex:
    — NOTE: HTTP_HOST is created dynamically by php based on the value of
   the HTTP HOST Header in the request, thus possibly allowing for file inclusion
   vulnerabilities. SERVER_NAME may also be created dynamically. However, when Apache
   is configured as UseCanonicalName “on”, SERVER_NAME is set by the server configuration,
   instead of dynamically. In that case, it is safer to user SERVER_NAME than HTTP_HOST.—-
   I am experiencing the same thing that wadegibson is (#1 logout issues). I believe
   this is related to the new .php file class-wp-user-meta-session-tokens.php in
   the includes directory – it’s new and deals with the tokens. It’s 100% reproducible.
   Copy 4.6 files to the core and everything is fine…copy the 4.7 files to the core
   and it’s broken.
 * This is clearly a ‘4.7 with multisite turned on’ issue and should be addressed
   in the code with an emergency fix release.
 * We should remove the ‘resolved’ from this thread as the HTTP_HOST solution should
   only be considered a workaround at this point – and, according to much discussion,
   an insecure one at that.
 * I hope you all agree.
 * DC
    -  This reply was modified 9 years, 3 months ago by [fwdcar](https://wordpress.org/support/users/fwdcar/).
 *  [fwdcar](https://wordpress.org/support/users/fwdcar/)
 * (@fwdcar)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8611728)
 * been dabbling a bit trying to figure out why setting these defines fixes the 
   logout problem.
 * Found out that I can also fix it by just adding this one line to wp-config.php:
 * define( ‘WP_SITEURL’, ‘USELESS-JUNK’ );
 * Yep, setting wp_siteurl to anything will fix the logout issue described by [@wadegibson](https://wordpress.org/support/users/wadegibson/).
 * So, something is going on in the code.
 * [@wadegibson](https://wordpress.org/support/users/wadegibson/) can you unresolve
   this thread?
 *  Thread Starter [wadegibson](https://wordpress.org/support/users/wadegibson/)
 * (@wadegibson)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8613333)
 * [@fwdcar](https://wordpress.org/support/users/fwdcar/) Thank you for the updates.
   I’ve marked the thread as unresolved.
 *  [fwdcar](https://wordpress.org/support/users/fwdcar/)
 * (@fwdcar)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8613856)
 * Thanks Wade….
 * When you get a chance, can you confirm my findings and see if it solves your #
   2 problem as well?
 * Remove your
 * `define( 'WP_HOME', '//' . $_SERVER['HTTP_HOST'] );`
 * and change your WP_SITEURL to:
 * `define( ‘WP_SITEURL’, ‘USELESS-JUNK’ );`
 * Thanks again…
 *  Thread Starter [wadegibson](https://wordpress.org/support/users/wadegibson/)
 * (@wadegibson)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8618491)
 * [@fwdcar](https://wordpress.org/support/users/fwdcar/) – Yes, I just removed 
   the WP_HOME setting and changed WP_SITEURL per your instructions. I confirmed
   that Logout still works and password protected pages/posts work.
 * However, I also see that I have $_SERVER[‘HTTP_HOST’ defined under the Multisite
   settings in my wp-config.php. Should it not be there either? It was a copy/paste
   directly from the WP-Multi-Network plugin instructions here ==> [https://github.com/stuttter/wp-multi-network](https://github.com/stuttter/wp-multi-network)
 * // Multisite
    define( ‘MULTISITE’, true ); define( ‘SUBDOMAIN_INSTALL’, false);
   define( ‘PATH_CURRENT_SITE’, ‘/’ ); define( ‘DOMAIN_CURRENT_SITE’, $_SERVER[‘
   HTTP_HOST’] );
 *  [fwdcar](https://wordpress.org/support/users/fwdcar/)
 * (@fwdcar)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8618578)
 * Hi Wade…A couple of things….
    First, great that you can confirm my findings…I
   hope that someone from WordPress will read the thread and figure out what’s up
   with the code. Secondly, I too am using multi-‘network’. I’m using this plugin:
   [https://wordpress.org/plugins/wp-multi-network/](https://wordpress.org/plugins/wp-multi-network/).
   If you click on that link and look at the ‘installation’, is says to comment 
   out the ‘DOMAIN_CURRENT_SITE’ line. The GitHub link you posted also says this
   in the ‘Installation’ section just above what you posted.
 * I’m thinking maybe they were just showing what it looks like before the change?
   I don’t know, but it is confusing. For what it’s worth, mine is commented out
   per the installation instruction on the plugin site.
 * This is what the multisite section of my wp-config looks like:
 *     ```
       /* Multisite */
       define( 'WP_ALLOW_MULTISITE', true );
       define('MULTISITE', true);
       define('SUBDOMAIN_INSTALL', false);
       /* define('DOMAIN_CURRENT_SITE', 'www.sample.com');*/
       define('PATH_CURRENT_SITE', '/');
       define('SITE_ID_CURRENT_SITE', 1);
       define('BLOG_ID_CURRENT_SITE', 1);
       ```
   
 * Hope this helps….
 *  Thread Starter [wadegibson](https://wordpress.org/support/users/wadegibson/)
 * (@wadegibson)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/#post-8618634)
 * Good catch. I noticed they mentioned that on v1.8.1 in the WP repo, but I didn’t
   see it on the GitHub instructions.

Viewing 15 replies - 1 through 15 (of 22 total)

1 [2](https://wordpress.org/support/topic/4-7-multi-network-issues/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/4-7-multi-network-issues/page/2/?output_format=md)

The topic ‘4.7 Multi Network Issues’ is closed to new replies.

## Tags

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

 * In: [Networking WordPress](https://wordpress.org/support/forum/multisite/)
 * 22 replies
 * 7 participants
 * Last reply from: [Amibe Websites](https://wordpress.org/support/users/amibe/)
 * Last activity: [8 years, 11 months ago](https://wordpress.org/support/topic/4-7-multi-network-issues/page/2/#post-9040996)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
