I’m getting an AccessDenied error in my blocks

Getting an "AccessDenied" block error usually happens when there is an icon in the block.

How to troubleshoot this error:

1. Check if you have a security solution or plugin

If you are using a custom SVG icon, it may have something to do with a security solution or plugin that you have.

The “Access Denied” block errors could be related to how security plugins handle file types and permissions when using custom SVGs.

2. Check if the page containing the block errors is a duplicated page that was created using a duplicating plugin

Block errors like this usually occur if the page undergoes some processing that is not compatible with Gutenberg. Usually this happens with Duplicate Page plugins where you need to first set it to Gutenberg.

Read more about it here: I’m getting block errors when I duplicate a page

The corruption of the SVGs or icons are usually from some processing that's performed on the page content, outside of Stackable, that is not compatible with Gutenberg/Block Editor. This is not specifically for Stackable only, but for SVGs in general in a page.

How to fix the blocks that encounter the error

If you have already addressed the possible causes above, refreshing the editor should make the blocks work again. If afterwards, you are still seeing the “AccessDenied” error, then unfortunately the blocks have been modified already and the only way to address this is to re-create the blocks.