Title: Plugin causes fatal error Last modified: November 14, 2019 --- # Plugin causes fatal error * Resolved [Chris J. Zähller](https://wordpress.org/support/users/seezee/) * (@seezee) * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/) * I’ve been using this plugin for several years. Yesterday’s it started causing a fatal error that put the site into safe-mode. I’ve had to disable it entirely. * > Howdy! > Since WordPress 5.2 there is a built-in feature that detects when a plugin > or theme causes a fatal error on your site, and notifies you with this automated > email. > In this case, WordPress caught an error with one of your plugins, wp-Typography. * And: * > Error Details > ============= An error of type E_ERROR was caused in line 117 > of the file /path/to/wp-typography/vendor/masterminds/html5/src/HTML5/Parser/ > DOMTreeBuilder.php. Error message: Uncaught Error: Class ‘DOMImplementation’ > not found in /path/to/wp-typography/vendor/masterminds/html5/src/HTML5/Parser/ > DOMTreeBuilder.php:117 Stack trace: #0 /path/to/wp-typography/vendor/masterminds/ > html5/src/HTML5.php(144): WP_Typography\Vendor\Masterminds\HTML5\Parser\DOMTreeBuilder- > >__construct() #1 /path/to/wp-typography/vendor/masterminds/html5/src/HTML5. > php(81): WP_Typography\Vendor\Masterminds\HTML5->parse() #2 /path/to/wp-typography/ > vendor/mundschenk-at/php-typography/src/class-php-typography.php(220): WP_Typography\ > Vendor\Masterminds\HTML5->loadHTML() #3 /path/to/wp-typography/vendor/mundschenk- > at/php-typography/src/class-php-typography.php(153): PHP_Typography\PHP_Typography- > >parse_html() #4 /path/to/wp-typography/vendor/mundschenk- - This topic was modified 6 years, 7 months ago by [Chris J. Zähller](https://wordpress.org/support/users/seezee/). * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-causes-fatal-error-3%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 6 replies - 1 through 6 (of 6 total) * Plugin Author [pepe](https://wordpress.org/support/users/pputzer/) * (@pputzer) * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/#post-12133203) * The most likely reason is that your memory limit is set too low and wp-Typography happens to be the plugin that reaches it. You should find the exact error message in the PHP log. * Plugin Author [pepe](https://wordpress.org/support/users/pputzer/) * (@pputzer) * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/#post-12133218) * OK, no, that is something different (didn’t see the edit before). I assume you recently changed your PHP installation, because it appears the DOM extension has been deactivated somehow. It is [enabled by default](https://www.php.net/manual/en/dom.installation.php), but some distributors disable it. - This reply was modified 6 years, 7 months ago by [pepe](https://wordpress.org/support/users/pputzer/). Reason: Added link for DOM extension * Thread Starter [Chris J. Zähller](https://wordpress.org/support/users/seezee/) * (@seezee) * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/#post-12133884) * Yes, you’re right. I actually re-enabled the dom extension shortly before I saw your reply & just now checked — the plugin is working fine now. - This reply was modified 6 years, 7 months ago by [Chris J. Zähller](https://wordpress.org/support/users/seezee/). - This reply was modified 6 years, 7 months ago by [Chris J. Zähller](https://wordpress.org/support/users/seezee/). * Thread Starter [Chris J. Zähller](https://wordpress.org/support/users/seezee/) * (@seezee) * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/#post-12134795) * Sorry to bother you but it’s still causing errors. * PHP DOM extension is enabled. From phpinfo(): * DOM/XML enabled DOM/XML API Version 20031129 * Any other suggestions? It probably _is_ due to the PHP version switch but I have no idea which other extension might be missing. * Plugin Author [pepe](https://wordpress.org/support/users/pputzer/) * (@pputzer) * [6 years, 7 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/#post-12135784) * [@seezee](https://wordpress.org/support/users/seezee/) You might need to clear some cache(s). [`DOMImplementation` is an interface provided by the DOM extension](https://www.php.net/manual/en/class.domimplementation.php) and should be always available when this extension is enabled. * Or do you get another error message now? - This reply was modified 6 years, 7 months ago by [pepe](https://wordpress.org/support/users/pputzer/). Reason: Added question * Thread Starter [Chris J. Zähller](https://wordpress.org/support/users/seezee/) * (@seezee) * [6 years, 6 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/#post-12138045) * Clearing the cache didn’t work, but I had made some changes to the main php.ini. I rolled those back & it seems to have solved the problem. Thanks again for the quick response & helpful suggestions. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Plugin causes fatal error’ is closed to new replies. * ![](https://ps.w.org/wp-typography/assets/icon.svg?rev=2663995) * [wp-Typography](https://wordpress.org/plugins/wp-typography/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-typography/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-typography/) * [Active Topics](https://wordpress.org/support/plugin/wp-typography/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-typography/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-typography/reviews/) * 6 replies * 2 participants * Last reply from: [Chris J. Zähller](https://wordpress.org/support/users/seezee/) * Last activity: [6 years, 6 months ago](https://wordpress.org/support/topic/plugin-causes-fatal-error-3/#post-12138045) * Status: resolved