Conflict with Accordion Plugins

I have identified the conflicting feature as the “Custom Class Names”.

However, I am still unable to pinpoint what is causing the conflict with the Easy Accordion Block plugin. This feature has worked well in most cases, but it has caused conflicts with two plugins so far.

I suggest informing their support team of this issue and providing them with the code reference for this feature from Editor’s Kit. You can find the code reference here:

https://github.com/CakeWP/block-options/blob/master/src/extensions/advanced-controls/custom-class-name/index.js

I believe this has something for them, but you can disable the mentioned feature if you don’t use it and want to use both plugins.

Hope this helps.

Hi @munirkamal.

Thank you for the EditorsKit plugin. I am one of the authors of the Tainacan plugin and I too have identified this conflict with some of ours blocks. Basically, every time I call a useSelect inside a block, it triggers the error if the custom class names feature is enabled.

I also don’t understand the cause for this. I’ll just give you some links here that I believe may be useful if you want to investigate on your side:

This is the where the error message comes from in the Gutenberg source code:

https://github.com/WordPress/gutenberg/blob/7b334ff38ade601c41a49e4bba8034501c6b0926/packages/data/src/components/use-select/index.js#L264

Notice how it mentions this “static” vs “mapping” context change. I believe it may be related to different moments when the hook can be called. This StackOveflow topic made me believe it can be caused by invoking it multiple times in the same context, but I’m not familiar with hooks.

Looking into the EditorsKit plugin source code, the only curious thing that I can notice is that you are using withSelect instead of useSelect, which was introduced a few years ago and seems the be the more “canonical” approach according to the Gutenberg Documentation.

Hope this helps somehow finding a solution!