Common React and Gutenberg Errors
There are many common errors you may encounter within the Block Editor or React. React-specific errors usually output an error link which would lead you to the Error Decoder (opens in a new tab).
Running code in "development" mode (unminified) will probably be more helpful in debugging errors than running in production mode.
Block Failures
This is almost certainly a result of a JavaScript error if the block throwing this error uses a dynamic render callback (opens in a new tab). It may also be an issue with a conflict in what was expected from post_content and what was returned if the block is using the legacy save (opens in a new tab) method.
- Have you recently built your plugin?
- Look at the console logs in-browser and see if there are any helpful notes or errors.
- Does this only happen during certain circumstances? It could be that your block has a race condition, invalid names for variables or functions, or is returning a value that is unexpected.
Block Unavailable
This is typically the result of a registration issue. Either the block was available, but is no longer, the block is in someway broken or incomplete, or the block is not being properly registered.
- Have you recently built your plugin?
- Is the block enabled in the config for the brand you're working on?
- Can you confirm that the script for the block is being enqueued? You may see a 404 error in the browser's console logs.
- Have you recently renamed the block?