Closed joshuadavidnelson closed 2 years ago
Noting here: The solution in v0.5.1 to this was broad - disabling blocks in the editor related to posts - and causes other issues in the block editor & full site editing (FSE) mode. So, version 0.5.2 will revert this fix.
The only actual fallout from this issue is a console error, which is fine, really. The user will still see term-specific blocks, and they'll present with an error on the block output: "Term items not found" message in the editor and no output for the block on the front-end. This is a reasonable way to handle using a block that has no content to present.
A separate issue will be tackling block editor features in a future release.
Reported in this support forum post, the block editor throws errors when trying to reference taxonomy endpoints. A future release should do a better job of removing post related blocks and taxonomy related blocks, when not supported by custom types/taxonomies.