• Resolved benkerve

    (@benkerve)


    Hi,

    Im running v1.8.2 on a WordPress v6.1.1 multisite (1 main site, 16 child “sub” sites). Multisite is running domain driven (so a different domain mapped to each subsite).

    Installing Prime Mover went fine, however when I “active” the plugin (ie. Network Activate) so I can clone/backup a subsite, it caused one of my subsites (blog ID 8) to break publicly (ie. anyone visiting this site’s domain that isn’t logged into the WordPress admin is presented with content coming in from the main site, no theme being used, meta data all wrong, content missing (ie. page content) etc. However if an admin user logs into the admin, then viewed the site, it works and looks fine, as intended.

    This doesn’t happen for any of the other subsites. Just blog ID 8.

    I have tested this on multiple servers including a development environment that runs different content. It still causes an issue on a blog ID 8.

    When you Deactivate the Prime Mover plugin, the broken sites starts working as it should do.

    Any thoughts?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Codexonics

    (@codexonics)

    Hello, thanks for using Prime Mover! The issue looks weird as it happens only on blog ID 8 but other sites unaffected. And it works if admin is logged into but not a public user.

    Would it be possible for you to do these troubleshooting steps and provide us the data?

    • Make sure Prime Mover is deactivated.
    • Login to blog ID 8 subsite -> WordPress admin.
    • Go to Tools -> SiteHealth -> Info.
    • Click “Copy site info” to clipboard.
    • Paste that to text editor and save it as blogid8-siteinfo.txt.
    • Enable WordPress debugging and add this to your wp-config.php:
    // Enable WP_DEBUG mode
    define( 'WP_DEBUG', true );
    
    // Enable Debug logging to the /wp-content/debug.log file
    define( 'WP_DEBUG_LOG', true );
    
    // Disable display of errors and warnings
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
    • Make sure no debug.log is generated in /wp-content/
    • Login to Network admin.
    • Quickly network activate Prime Mover plugin.
    • On another browser (logged-out) – visit the subsite (blog ID 8) as a public user to confirm the issue.
    • Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Upload/Download Parameters -> Export site info and click “Export site info“. This will download your site info details including your Prime Mover settings data. This is your site information log.
    • Once the site information is downloaded – network deactivate Prime Mover.
    • Zip all three important logs (blogid8-siteinfo.txt, site information log generated, debug.log (if its generated in wp-content directory)
    • Please send us the link to download this zip (containing these logs) to our support contact page. Please don’t share it here because it contains sensitive information.
    • You can now safely disable WordPress debugging by removing the above code in your wp-config.php. And delete the debug.log in /wp-content/ directory.

    Once you’ve send us the logs – please give us time to check and reproduce this issue. It’s possible there could be some plugin or theme conflicts that is causing this. Or it could just be a caching issue. Thanks!

    • This reply was modified 1 year, 8 months ago by Codexonics.
    Plugin Author Codexonics

    (@codexonics)

    As an update – I’m closing this ticket because it’s now outdated. Prime Mover 1.8.3 is released today and includes the latest bugs fixes. Please update and use the latest version. If there is still an issue – please let us know and provide us all the details. Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Making it Network Active on Multisite Breaks a subsite’ is closed to new replies.