Any other reasons for a fatal error?

Hello.

Try to disable all third party plugins to investigate the issue. Let us know the results.

Thanks.

@awetherillweb – as Maria mentioned, please disable one plugin at a time until you notice the fatal error resolved. Once you identify the conflicting plugin, please let us know and we can replicate and fix the issue for a patch release.

If disabling plugins doesn’t change anything, it could be with your theme. Try temporarily disabling the theme to see if it is resolved as well.

Let us know your findings so we can get to work on a patch for you. Thanks! ??

If that doesn’t work, please shoot me an email at [email protected] so that I can take a closer look. Thank you

• This reply was modified 7 years, 2 months ago by Eric Sopp.

Same problem. I’ve tried with all other plugins deactivated and the error persists:

Fatal error: Uncaught Error: Call to a member function refresh() on null in
\wp-content\plugins\wp-stateless\lib\classes\class-bootstrap.php:289
Stack trace:
#0 \wp-includes\class-wp-hook.php(298): wpCloud\StatelessMedia\Bootstrap->on_switch_blog(1, 1)
#1 \wp-includes\class-wp-hook.php(323): WP_Hook->apply_filters(”, Array)
#2 \wp-includes\plugin.php(453): WP_Hook->do_action(Array)
#3 \wp-includes\ms-blogs.php(819): do_action(‘switch_blog’, 1, 1)
#4 \wp-includes\link-template.php(3067): switch_to_blog(1)
#5 \wp-includes\link-template.php(3118): get_site_url(1, ‘wp-admin/’, ‘admin’)
#6 \wp-content\plugins\wp-stateless\lib in \wp-content\plugins\wp-stateless\lib\classes\class-bootstrap.php on line 289

Hello @pirayax – can you please update wp-stateless with this hotfix release? https://github.com/wpCloud/wp-stateless/archive/v2.0-hotfix.zip

Let me know if this resolves your problem. Thanks!

Hi Eric, the hotfix worked very good so far.
Thanks very much!

That’s great – thank you for confirmation. We’ll be sure to include that in the next official release.

Cool!
Good job BTW.
Thanks again for your plugin, very useful!

This fix has been officially released in v2.0.3. Thanks for the report and troubleshooting.