Support » Fixing WordPress » FATAL ERROR after plugin update

  • Hello,

    Posting this here as not sure where to begin.

    My site has/is working fine on the front end but when I go to ‘edit pages’ from the dashboard area I am led to a ‘fatal error’ message.

    This has only happened since updating the Ultimate Addons for Gutenberg plugin by Brainstorm. I’ve contacted them about it and they suggest that because it works fine on different WordPress themes it’s a problem with TwentySeventeen.

    My site uses the TwentySeventeen theme.

    Here’s the message, any advice appreciated:

    Fatal error: Uncaught Error: Call to a member function prepare_assets() on null in /home/customer/www/ Stack trace: #0 /home/customer/www/ UAGB_Twenty_Seventeen_Compatibility->generate_stylesheet(Object(WP)) #1 /home/customer/www/ WP_Hook->apply_filters(NULL, Array) #2 /home/customer/www/ WP_Hook->do_action(Array) #3 /home/customer/www/ do_action_ref_array('wp', Array) #4 /home/customer/www/ WP->main(Array) #5 /home/customer/www/ wp(Array) #6 /home/customer/www/ in /home/customer/www/ on line 62
    There has been a critical error on this website. Please check your site admin email inbox for instructions.
    Learn more about troubleshooting WordPress.
Viewing 3 replies - 1 through 3 (of 3 total)
  • That message shows that the plugin has a special code file for handling Twenty Seventeen, and that is what is failing. The theme is not the problem. The plugin is causing the error.
    You can switch themes if they don’t want to fix it. Or don’t use that plugin if you want to keep the theme.

    Thread Starter joelkarate


    Thank you,
    After all the work I’ve done so far, I’ll opt to do without the plugin.
    TwentySeventeen should have another year or two in it yet no?

    Yes, we are still adding latest stuff to Twenty Ten, haha! I was recently asking why we want to support an eleven year old theme, and as time goes on we have more and more themes to support if we never drop the old ones.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘FATAL ERROR after plugin update’ is closed to new replies.