Making it Network Active on Multisite Breaks a subsite

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, 1 month ago by Codexonics.