Breaks site signup

Resolved

(@ravanh)

Hi, first: thank you for this great and useful plugin!

I ran into an issue: when Prime Mover is active on the network, I cannot create new sites. It gives me this error when WP_DEBUG is on:

[10-Dec-2025 11:16:24 UTC] PHP Fatal error:  Uncaught Error: Call to a member function exists() on null in /home/xxx/xxx/wp-content/plugins/prime-mover/classes/PrimeMoverSystemInitialization.php:1907
Stack trace:
#0 /home/xxx/xxx/wp-content/plugins/prime-mover/classes/PrimeMoverSystemInitialization.php(1893): Codexonics\PrimeMoverFramework\classes\PrimeMoverSystemInitialization->putContents()
#1 /home/xxx/xxx/wp-content/plugins/prime-mover/classes/PrimeMoverSystemInitialization.php(1781): Codexonics\PrimeMoverFramework\classes\PrimeMoverSystemInitialization->initializeIndexHTML()
#2 /home/xxx/xxx/wp-content/plugins/prime-mover/compatibility/PrimeMoverCleanUp.php(424): Codexonics\PrimeMoverFramework\classes\PrimeMoverSystemInitialization->camouflageFolders()
#3 /home/xxx/xxx/wp-includes/class-wp-hook.php(341): Codexonics\PrimeMoverFramework\compatibility\PrimeMoverCleanUp->autoCreateExportFolderOnBlogCreation()
#4 /home/xxx/xxx/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#5 /home/xxx/xxx/wp-includes/plugin.php(522): WP_Hook->do_action()
#6 /home/xxx/xxx/wp-includes/ms-site.php(89): do_action()
#7 /home/xxx/xxx/wp-includes/ms-functions.php(1440): wp_insert_site()
#8 /home/xxx/xxx/wp-signup.php(506): wpmu_create_blog()
#9 /home/xxx/xxx/wp-signup.php(999): validate_another_blog_signup()
#10 {main}
  thrown in /home/xxx/xxx/wp-content/plugins/prime-mover/classes/PrimeMoverSystemInitialization.php on line 1907

The new site will appear in the Network > Sites list but it cannot be accessed or modified. Database tables are not created.

Note: the network is set to only allow site creation for registered users. Other network activated plugins: Jetpack, Litespeed Cache, Multisite Enhancements.

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

Plugin Author Codexonics
(@codexonics)

5 months, 2 weeks ago

Hello Rolf,

Thank you for using the Prime Mover plugin! I’m sorry to hear you’re having issues with the plugin on your site. We’ve checked the error stack, and your site does not consistently set the $wp_filesystem global object.

We’ve tried to reproduce this on our test servers (both local and remote, across different hosting companies, including popular ones), but couldn’t see the problem.

However, we have found a simple workaround: we check whether $wp_filesystem is set before using it. If not set, we initialize the WP Filesystem object so it’s usable. We hope this works with your setup; otherwise, there is no quick workaround for now except to deactivate the plugin while we work on a different solution.

You can download the hotfix here: https://codexonics.com/prime-mover/hotfix/prime-mover-free.2.1.1-hotfix.zip

Please try it on your site and see if it works. You need to delete the current version and replace it with the hotfix version. We will add a permanent fix in the next release, 2.1.2, but for now, please use the hotfix version. Thanks, and please mark the ticket as resolved if it works for you

Cheers!

Thread Starter Rolf Allard van Hagen
(@ravanh)

5 months, 2 weeks ago

Strange how $wp_filesystem is not being set globally. Is there any specific reason why this would happen? Site Health does not show any missing PHP modules or server incompatibilities.

I do have define( 'DISALLOW_FILE_EDIT', true ); in wp-config.php…

Plugin Author Codexonics
(@codexonics)

5 months, 2 weeks ago

Yeah, this is weird. We did some updated tests as follows (based on your latest post).

1.) In a multisite network activate the following plugins: Jetpack, Litespeed Cache, and Multisite Enhancements

2.) In wp-config, add the following constant:

define( 'DISALLOW_FILE_EDIT', true);

3.) In the network, go to Sites -> Add site -> then create a test subsite.

Expected: The issue is reproduced.
Actual result: The site is successfully created, with both front-end and back-end accessible.

My test environment is PHP 8.2.29 in Linux (PHP-fpm) + WordPress 6.9. Please provide more information about your site from the site health tools (e.g., a complete list of your plugins/themes/PHP info/server info). That would be great, so we can update our test site to make this reproducible.

If you have managed to activate the Prime Mover plugin using the hotfix version, you can also send us your site information, which is more complete than the one in Site Health Tools. Go to Prime Mover -> Advanced -> Advanced Settings Panel -> Upload/Download Parameters -> Export site info and click “Export site info“. This will download details of your site, including your Prime Mover settings. This is your site information log. Zip it and then share the download link to our tech team in this contact form.

This is likely an incompatibility issue with your server (perhaps a permission misconfiguration) or with one or more plugins. Still, until you can share all the details, we won’t have a better picture of this issue.

You can also create a test multisite (ideally a fresh one without any plugins and using default themes) on your server to play with and see if the issue is still reproducible with that test site. If it is reproducible, it might be hosting-related, so we need to know where your site is hosted so our tech team can run some tests.

Thanks again!

Plugin Author Codexonics
(@codexonics)

5 months, 2 weeks ago

OK, as an update, we have reproduced this when creating a site via the wp-signup.php page (not on Network admin -> Sites). I’m sorry, but this is not an issue with your server, plugins/themes. But this is currently a bug in Prime Mover: it can’t properly initialize the WP filesystem when used in the signup page.

We tested the hot fix as a workaround, and it works in this case so you can use it temporarily. We will add a permanent fix to the next release. Thank you again for reporting this issue!

Thread Starter Rolf Allard van Hagen
(@ravanh)

5 months, 2 weeks ago

Oww, I so regret not mentioning this happens on wp-signup.php and not on the network admin! It would have saved you much time. I’m very sorry.

Thank you so much for your patience and fix 🙂

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

You must be logged in to reply to this topic.