Title: Fatal Error after Gutenberg update Last modified: December 14, 2018 --- # Fatal Error after Gutenberg update * Resolved [arturo56k](https://wordpress.org/support/users/arturo56k/) * (@arturo56k) * [7 years, 5 months ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/) * The plugin use to work fine before. After latest worpress update i have installed“ Clasic Editor” plugin to disable gutenberg. The site was working fine before your last update. * After your latest update Versión 2.6.3 i get: * Parse error: syntax error, unexpected ‘=’, expecting ‘)’ in /public_html/wp-content/ plugins/tlp-portfolio/lib/classes/TLPPortfolioGutenBurg.php on line 42 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-error-after-gutenberg-update%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 11 replies - 1 through 11 (of 11 total) * Thread Starter [arturo56k](https://wordpress.org/support/users/arturo56k/) * (@arturo56k) * [7 years, 5 months ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-10989690) * I’ve downgraded it to 2.6.2 and it work fine * Plugin Author [RadiusTheme](https://wordpress.org/support/users/techlabpro1/) * (@techlabpro1) * [7 years, 5 months ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-10991574) * Hello, * The issue is fixed at the new version 2.6.31. * Thanks * Thread Starter [arturo56k](https://wordpress.org/support/users/arturo56k/) * (@arturo56k) * [7 years, 5 months ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-10991583) * Thanks you very much. it’s working now * Plugin Author [RadiusTheme](https://wordpress.org/support/users/techlabpro1/) * (@techlabpro1) * [7 years, 4 months ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11086239) * Hello, I am making this topics as resolved. If need any more help please let me know. * Thanks * [brusse11](https://wordpress.org/support/users/brusse11/) * (@brusse11) * [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11335845) * I have just updated Gutenberg to the latest version and now can not access my admin at all. I get a fatal error page instead. See below. How do I get this resolved? This is very frustrating. [https://cambridgereagents.co.uk/wp-admin/](https://cambridgereagents.co.uk/wp-admin/) * Fatal error: Uncaught Error: Call to a member function is_block_editor() on null in /home/cambr060/public_html/wp-content/plugins/gutenberg/gutenberg.php:97 Stack trace: #0 /home/cambr060/public_html/wp-content/plugins/envira-gallery/src/Admin/ Admin_Container.php(124): is_gutenberg_page() #1 /home/cambr060/public_html/wp- includes/class-wp-hook.php(286): Envira\Admin\Admin_Container->maybe_activate_gutenberg(”)# 2 /home/cambr060/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters( NULL, Array) #3 /home/cambr060/public_html/wp-includes/plugin.php(465): WP_Hook- >do_action(Array) #4 /home/cambr060/public_html/wp-admin/admin.php(169): do_action(‘ admin_init’) #5 /home/cambr060/public_html/wp-admin/themes.php(10): require_once(‘/ home/cambr060/…’) #6 {main} thrown in /home/cambr060/public_html/wp-content/plugins/ gutenberg/gutenberg.php on line 97 * Plugin Author [RadiusTheme](https://wordpress.org/support/users/techlabpro1/) * (@techlabpro1) * [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11335904) * Hello, * Are you using latest version of plugin? Please check your server PHP version? * Thanks * [brusse11](https://wordpress.org/support/users/brusse11/) * (@brusse11) * [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11335941) * I can’t check anything as I am shut out of my admin! * [brusse11](https://wordpress.org/support/users/brusse11/) * (@brusse11) * [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11335947) * However, I did update to the latest WordPress and woocommerce yesterday and all my other updates were current. * [brusse11](https://wordpress.org/support/users/brusse11/) * (@brusse11) * [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11336078) * Found it! PHP 7.0.33 * Plugin Author [RadiusTheme](https://wordpress.org/support/users/techlabpro1/) * (@techlabpro1) * [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11336269) * Hello, * Error coming from Gutenberg plugin see error file path not from our plugin. * Like * /home/cambr060/public_html/wp-content/plugins/gutenberg/gutenberg.php on line 97 * Plugin Author [RadiusTheme](https://wordpress.org/support/users/techlabpro1/) * (@techlabpro1) * [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11336274) * Please ask Gutenberg forum support. Viewing 11 replies - 1 through 11 (of 11 total) The topic ‘Fatal Error after Gutenberg update’ is closed to new replies. * ![](https://ps.w.org/tlp-portfolio/assets/icon-256x256.gif?rev=3456971) * [Radius Portfolio – Filterable Grid, Gallery & Slider Portfolio](https://wordpress.org/plugins/tlp-portfolio/) * [Frequently Asked Questions](https://wordpress.org/plugins/tlp-portfolio/#faq) * [Support Threads](https://wordpress.org/support/plugin/tlp-portfolio/) * [Active Topics](https://wordpress.org/support/plugin/tlp-portfolio/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/tlp-portfolio/unresolved/) * [Reviews](https://wordpress.org/support/plugin/tlp-portfolio/reviews/) ## Tags * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/) * [site down](https://wordpress.org/support/topic-tag/site-down/) * 11 replies * 3 participants * Last reply from: [RadiusTheme](https://wordpress.org/support/users/techlabpro1/) * Last activity: [7 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-after-gutenberg-update/#post-11336274) * Status: resolved