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 7 replies - 16 through 22 (of 22 total)

  • Update: Hey wade, after reading that section that you posted from github again, it appears it’s what you should do if you want ‘Domain/Sub-domain flexibility’. Not sure what it means, and they do indicate that ‘You’ll likely need some server configuration outside of WordPress to help with this…’. So, it appears at first glance it’s another way to configure multi-network.
    In either event, perhaps the security vulnerability of using HTTP_HOST is limited to certain usage. I only know that I’ve read a few times that using it was unsecure. Here’s the link to the codex that talks about it: https://codex.www.ads-software.com/Editing_wp-config.php. Scroll down to the WP_SITEURL section and check it out. I also remember reading about it on other sites as well.

    Later…..

    I am seeing the same issues in a multisite setup. Adding the define( ‘WP_SITEURL’, ‘USELESS-JUNK’ ); takes care of the issue but I have some multisites that do not see the issue with out the modification even though our multisites are all very similar. There have been other threads on this same issue. https://www.ads-software.com/support/topic/cant-preview-posts-or-private-posts/#post-8676382

    Hi Mishaua,

    There’s a ticket that was opened for it but it still shows a status of ‘awaiting review’:
    https://core.trac.www.ads-software.com/ticket/39497
    Hopefully someone will see review it soon.

    Interesting about your sites without the issue. Perhaps you can add the specifics (if there are any) to the ticket in hopes of helping better identify the source of the bug to whomever reviews the ticket.

    I tried 4.7.1 and the problem still exists…

    • This reply was modified 8 years, 1 month ago by fwdcar.
    • This reply was modified 8 years, 1 month ago by fwdcar.

    From the a couple of sites that seem to work with no problems, their initial create date (registered) is a little newer than the ones that have problems. I am looking the oldest top level network site. Is there a changelog or way to track upgrades in the database to determine what version the site started out with?

    not that i’m aware of. The only db versioning I’ve seen is in the table wp_blog_versions, but that just shows the current db version for the blogs.

    I was having a similar issue with nonces not working correctly for allowing users to Preview Changes in Posts/Pages and asking them if they were sure when they tried to log out.

    This solution worked like a charm, thank you!!!

    FYI, as per TRAC ticket referred by @fwdcar above, it appears this issue will be resolved in the release of 4.7.4

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘4.7 Multi Network Issues’ is closed to new replies.