A common issue users experience on WordPress 7.0+ is the block editor unresponsive or missing features. This can show up as "the editor is broken," "blocks won't do X anymore," or "this stopped working after we updated WordPress."
Cause: WordPress 7.0+ changed how block registrations are handled. When an outdated plugin is still registering blocks under an older block API version (v1/v2), that stale registration interferes with newer registrations (v3) on the same site.
Feast's own blocks are on API version 3, so this shows up as Feast blocks (or the editor generally) misbehaving even though the actual conflict is coming from a third-party plugin that hasn't been updated for the WP 7.0+ change.
Check: confirm the site is on WP 7.0+, then check the plugin list for anything outdated, especially plugins that register their own blocks (page builders, form plugins, other block libraries).
Fix, in order:
- Update any outdated plugins first — this resolves it in some cases
- If that doesn't fix it, deactivate plugins one at a time, refreshing the page with the issue after each deactivation, until the problem clears. The deactivated plugin that fixes the issue is likely the culprit
- For further troubleshooting (advanced), you can open the console log in your browser while in the block editor to view which errors are being thrown and sometimes, the source of that issue
As noted above, deactivating the Feast Plugin can sometimes make it appear that the Feast Plugin is the issue, because we're registering our blocks in the proper way (v3) in WordPress 7.0+, which creates a conflict with the outdated (v1, v2) blocks. The outdated blocks are the root cause of the issue.