iso.blocks.allowBlocks is ignored

[hawkidoki]

Hello!

I would like to report an issue which seems to be present since at least ISO 2.26.0 release. The following ISO settings are ignored when used on a WordPress website:

iso.blocks.disallowBlocks and iso.blocks.allowBlocks.

These settings were working fine before, but now all WordPress blocks are always allowed, whether these settings are filled or not (same behavior in ISO 2.27.0).

Blocks Everywhere, which use ISO, added the following code as a workaround since their 1.20 update (which use ISO 2.26.0):

function RemoveBlockTypes() {
	useEffect( () => {
		const blocks = getBlockTypes()
			.filter( ( block ) => wpBlocksEverywhere.iso.blocks.allowBlocks.indexOf( block.name ) === -1 )
			.forEach( ( block ) => {
				unregisterBlockType( block.name );
			} );
	}, [] );

	return null;
}

// ...
<IsolatedBlockEditor
        // ...
	<RemoveBlockTypes />
</IsolatedBlockEditor>

As you can see it now unregister unwanted blocks, which might be fine in their case (single editor instance). But if you have multiple editor instances and use this workaround, it will break other editors that want to use a previously unwanted block.

I didn't see this issue posted here and it seems that Block Everywhere decided to implement this workaround without reporting it. Are you aware of this issue? Is this intended? Do you have any workaround which would not require to unregister block types?

Thanks!

Regards.

[johngodley]

It is a new requirement of Gutenberg, not the isolated block editor. I don't know why the change was made, and that workaround is one that works for Blocks Everywhere. For the moment you will have to do whatever is needed for your usage.

[hawkidoki]

Hello!

Okay, thanks for the prompt answer. I will try to find a better workaround.