Hello @pagup,
I’m sorry about your experience. If your site uses a cache plugin or service, like Cloudflare, please clear the site and server caches. The plugin or service’s support team and your web host can help you clear the cache from these services. After removing the other caches on your site, please use this guide — https://yoa.st/3ve — to clear your browser cache.
Thread Starter
Pagup
(@pagup)
Hello,
Thanks for your reply. I can confirm that this issue is not related to caching.
Here’s the situation in detail:
- All plugins have been fully deactivated, except Yoast SEO, and the problem still occurs.
- There is no caching active on the site: WP Rocket is disabled, no object cache is running, and Cloudflare’s cache has been purged.
- The issue happens in the WordPress admin, when editing a page using WPBakery / Classic Editor, not Gutenberg.
- The JavaScript console shows the Yoast script attempting to call
(0, t.select(…)).getPostType is not a function
which is a function that only exists in the Gutenberg editor (wp.data.select('core/editor')).
- Since Gutenberg is completely disabled site-wide, this function cannot exist, and the error stops the Yoast metabox from loading properly.
This means the problem is not cache-related, but caused by Yoast loading its block-editor (Gutenberg) assets even when the editor is disabled.
Could you please escalate this to your technical team?
Ideally, the Yoast script should check whether use_block_editor_for_post_type() returns true before loading Gutenberg-dependent bundles like yoast-seo-post-edit or yoast-seo-premium-post-edit.
Thank you for reviewing this
I’ll be happy to provide full console logs or stack traces if needed.
Best regards,
Thread Starter
Pagup
(@pagup)
Hello Yoast Team,
I just wanted to confirm that the JavaScript error
(0, t.select(...)).getPostType is not a function
disappears completely after rolling back Yoast SEO to version 24.9.
This means the issue was introduced in a later release — likely from v25.x onward.
No cache, CDN, or other plugins are involved; the rollback alone resolves the problem instantly.
You might want to review changes made in the recent versions regarding how the plugin enqueues its block-editor assets (yoast-seo-post-edit, etc.) even when Gutenberg is disabled.
Best,
