Title: errors when writing the article Last modified: February 7, 2026 --- # errors when writing the article * Resolved [Phuong Tong](https://wordpress.org/support/users/tvphuong41/) * (@tvphuong41) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/errors-when-writing-the-article/) * > Minified React error #200; visit [https://reactjs.org/docs/error-decoder.html?invariant=200](https://reactjs.org/docs/error-decoder.html?invariant=200) > for the full message or use the non-minified dev environment for full errors > and additional helpful warnings. * I disabled all other plugins and installed only the Classic Editor plugin on the latest version of WordPress, and I’m still getting this error. Viewing 7 replies - 1 through 7 (of 7 total) * [Pouya](https://wordpress.org/support/users/pouyaebrhm/) * (@pouyaebrhm) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18814971) * Hi, This error isn’t caused by the Classic Editor plugin itself. * “Minified React error #200” means there’s a JavaScript error happening **before** the editor loads. Even if you’re using Classic Editor, WordPress still loads React/Gutenberg scripts in the admin. * A few things to check next: - Temporarily switch to a **default theme** (Twenty Twenty-Four / Twenty Twenty- Five) - Clear **all caches** (browser + server + CDN, if any) - Check the **browser console (F12 → Console)** for the full, non-minified error - Make sure your PHP version is compatible with your WordPress version (PHP 8.0–8.2 is safest) * If the error still appears with only a default theme and Classic Editor active, please share the **console error details**, as that’s the only way to pinpoint the exact cause. * Thread Starter [Phuong Tong](https://wordpress.org/support/users/tvphuong41/) * (@tvphuong41) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18814981) * I have installed each Yoast SEO theme: Active: Twenty Twenty-OneNo cachePHP 8.4 or 8.5 both have this error.F12 error : * ```wp-block-code react-dom.min.js?ver=18.3.1.1:10 Error: Minified React error #200; visit https://reactjs.org/docs/error-decoder.html?invariant=200 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at e.createPortal (react-dom.min.js?ver=18.3.1.1:10:126560) at Mo (block-editor.js?ver=19b0469618de7a408067:475:1436) at ht (react-dom.min.js?ver=18.3.1.1:10:45677) at Qs (react-dom.min.js?ver=18.3.1.1:10:120133) at wl (react-dom.min.js?ver=18.3.1.1:10:88341) at bl (react-dom.min.js?ver=18.3.1.1:10:88269) at yl (react-dom.min.js?ver=18.3.1.1:10:88132) at il (react-dom.min.js?ver=18.3.1.1:10:84984) at fl (react-dom.min.js?ver=18.3.1.1:10:85364) at Nn (react-dom.min.js?ver=18.3.1.1:10:32442) ``` * [Pouya](https://wordpress.org/support/users/pouyaebrhm/) * (@pouyaebrhm) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18815042) * Thanks for the details — this helps a lot. * The key issue here is the PHP version. **PHP 8.4 and 8.5 are not supported by WordPress yet**, and they are known to break parts of the admin UI, including React/Gutenberg. That’s why you’re seeing the React error even with a default theme and only Classic Editor active. * Please switch PHP to **8.1 or 8.2** (8.1 is the safest choice right now), then clear browser cache and reload the editor. * If the error still happens on PHP 8.1/8.2, then we can investigate further, but with 8.4/8.5 this behavior is expected and unsupported. * Thread Starter [Phuong Tong](https://wordpress.org/support/users/tvphuong41/) * (@tvphuong41) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18815055) * I switched to php 8.2 and still get the error * > ```wp-block-code > react-dom.min.js?ver=18.3.1.1:10 Error: Minified React error #200; visit https://reactjs.org/docs/error-decoder.html?invariant=200 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.at e.createPortal (react-dom.min.js?ver=18.3.1.1:10:126560)at Mo (block-editor.js?ver=19b0469618de7a408067:475:1436)at ht (react-dom.min.js?ver=18.3.1.1:10:45677)at Qs (react-dom.min.js?ver=18.3.1.1:10:120133)at wl (react-dom.min.js?ver=18.3.1.1:10:88341)at bl (react-dom.min.js?ver=18.3.1.1:10:88269)at yl (react-dom.min.js?ver=18.3.1.1:10:88132)at il (react-dom.min.js?ver=18.3.1.1:10:84984)at fl (react-dom.min.js?ver=18.3.1.1:10:85364)at Nn (react-dom.min.js?ver=18.3.1.1:10:32442) > ``` > * [Pouya](https://wordpress.org/support/users/pouyaebrhm/) * (@pouyaebrhm) * [3 months, 3 weeks ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18815083) * Hi, * This error confirms a **JavaScript / Gutenberg context issue**, not a PHP or Classic Editor problem. * `Minified React error #200` usually happens when Gutenberg tries to render a portal (toolbar, modal, popover) but the required DOM or editor context is missing or corrupted. * Common causes: - A theme or plugin overriding `wp-element`, `react`, or `react-dom` - Mismatched Gutenberg / WordPress core scripts - Editor scripts loading without the full editor container - Incompatible PHP versions (8.4 / 8.5 are **not supported** yet) * Important notes: - Classic Editor does **not** prevent Gutenberg scripts from loading - This error happens **before** the editor UI renders * Recommended next steps: - Downgrade PHP to **8.1 or 8.2** - Temporarily disable **all plugins except Classic Editor** - Switch to a default theme (Twenty Twenty-Four / Five) - Hard refresh browser + clear server cache - Check if the error disappears on a fresh install * If the error still occurs on a clean setup, this points to a core Gutenberg / React compatibility issue. * Plugin Support [Jose Varghese](https://wordpress.org/support/users/josevarghese/) * (@josevarghese) * [3 months, 2 weeks ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18824446) * Hi [@tvphuong41](https://wordpress.org/support/users/tvphuong41/) * Thanks for using Yoast SEO plugin and for opening the thread. Since you have already run the conflict check, have you tried clearing your browser and server caches to see if the problem persists? If you are using the Plugin Load Filter plugin on your website, we recommend deactivating and reactivating it, as some customers have reported that this workaround fixes the issue. * We look forward to hearing from you. * Thread Starter [Phuong Tong](https://wordpress.org/support/users/tvphuong41/) * (@tvphuong41) * [3 months, 1 week ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18827894) * Thank you, everything is working well. Viewing 7 replies - 1 through 7 (of 7 total) You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ferrors-when-writing-the-article%2F%3Foutput_format%3Dmd&locale=en_US) to reply to this topic. * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908) * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/) * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/) * 7 replies * 3 participants * Last reply from: [Phuong Tong](https://wordpress.org/support/users/tvphuong41/) * Last activity: [3 months, 1 week ago](https://wordpress.org/support/topic/errors-when-writing-the-article/#post-18827894) * Status: resolved