First of all, congratulations on the Montoya theme! I am currently building my design studio's website with it, and I absolutely love the design and the Elementor integration. It's a fantastic piece of work.
I'm reaching out because I ran into a technical hiccup while trying to use a modern Gutenberg-based plugin (Scrollsequence) alongside the theme.
While troubleshooting the issue with the plugin's developer, we noticed that my WordPress block editor is being forced to load in a legacy "non-iframe" mode. We checked the browser's console, and it pointed out that the montoya-gutenberg/moving-gallery block is currently registered with API version 1. (I've attached a screenshot of the console warning for your reference!).
Because of this API version, WordPress disables the modern iframe editor, which unfortunately breaks the compatibility with newer plugins that rely strictly on Block API v3.
I know Montoya focuses heavily on the Elementor side (which works flawlessly!), but since WordPress Core is pushing towards making iframe editors mandatory in the future, I wanted to kindly ask if there is any plan to update the Montoya Gutenberg blocks to apiVersion: 3 in an upcoming release?
I really want to keep using Montoya alongside this plugin to create a great experience for my visitors. Please let me know if there is any temporary workaround I could use, or if this is something you might consider updating soon.
Thank you so much for your time and for the great support!
Hi again! Just a quick note: I originally submitted this as a private ticket by mistake, but I decided to repost it publicly here. I figured that if anyone else in the community is running into the same compatibility issue, having this thread visible could be helpful to them too. Thanks again!
That was the right decision. This way we can share the solution with someone else who needs it.
Try this :
specify the explicit API version in the register_block_type call
so if you can go to /wp-content/plugins/montoya-gutenberg-blocks/blocks.js (path relative to the WordPress installation folder) and as an example, for the montoya-gutenberg/moving-gallery block
Thank you so much for the quick reply and for pointing me in the right direction!
I went ahead and added apiVersion: 3 exactly where you suggested in the blocks.js file for the moving-gallery block. I did a hard refresh, but unfortunately, the editor remained stuck in the legacy non-iframe mode.
I dug a little deeper into the developer console to see what was going on, and it looks like there are dozens of other blocks (like moving-gallery-image, buttons, marquees, scrolling panels, etc.) that are still throwing the exact same API v1 warning and breaking the iframe.
I was wondering: are you planning to release a theme update soon that adds apiVersion: 3 across all registered blocks?
I’ve attached a quick screenshot/recording of my console so you can see the warnings popping up!
Thanks again for your great support and taking the time to look into this with me.
as you can see from the code we are using the default value for the apiVersion parameter
If you like - if you can provide wp admin access with full rights using Plugin File Editor (in a private comment) we can modify the apiVersion for all createBlock function calls.
Hi Clapat Support Team,
First of all, congratulations on the Montoya theme! I am currently building my design studio's website with it, and I absolutely love the design and the Elementor integration. It's a fantastic piece of work.
I'm reaching out because I ran into a technical hiccup while trying to use a modern Gutenberg-based plugin (Scrollsequence) alongside the theme.
While troubleshooting the issue with the plugin's developer, we noticed that my WordPress block editor is being forced to load in a legacy "non-iframe" mode. We checked the browser's console, and it pointed out that the montoya-gutenberg/moving-gallery block is currently registered with API version 1. (I've attached a screenshot of the console warning for your reference!).
Because of this API version, WordPress disables the modern iframe editor, which unfortunately breaks the compatibility with newer plugins that rely strictly on Block API v3.
I know Montoya focuses heavily on the Elementor side (which works flawlessly!), but since WordPress Core is pushing towards making iframe editors mandatory in the future, I wanted to kindly ask if there is any plan to update the Montoya Gutenberg blocks to apiVersion: 3 in an upcoming release?
I really want to keep using Montoya alongside this plugin to create a great experience for my visitors. Please let me know if there is any temporary workaround I could use, or if this is something you might consider updating soon.
Thank you so much for your time and for the great support!
Best regards, João
Attached files: bug montoya.png
Hi again! Just a quick note: I originally submitted this as a private ticket by mistake, but I decided to repost it publicly here. I figured that if anyone else in the community is running into the same compatibility issue, having this thread visible could be helpful to them too. Thanks again!
Hello João,
That was the right decision. This way we can share the solution with someone else who needs it.
Try this :
specify the explicit API version in the register_block_type call
so if you can go to /wp-content/plugins/montoya-gutenberg-blocks/blocks.js (path relative to the WordPress installation folder) and as an example, for the montoya-gutenberg/moving-gallery block
you can say
Hard refresh (Ctrl+F5) before testing.
It looks like WordPress 7.0 will render the editor in an iframe, regardless
https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/
Thank you.
Clapat Support
Review Envato Item Support Policy
Follow us!
https://www.clapat.com/
https://www.facebook.com/clapat.ro
https://www.instagram.com/clapat.themes/
https://x.com/clapatdesign
https://www.linkedin.com/company/clapatstudio
https://www.tiktok.com/@clapatstudio
Hi again, Clapat Support!
Thank you so much for the quick reply and for pointing me in the right direction!
I went ahead and added apiVersion: 3 exactly where you suggested in the blocks.js file for the moving-gallery block. I did a hard refresh, but unfortunately, the editor remained stuck in the legacy non-iframe mode.
I dug a little deeper into the developer console to see what was going on, and it looks like there are dozens of other blocks (like moving-gallery-image, buttons, marquees, scrolling panels, etc.) that are still throwing the exact same API v1 warning and breaking the iframe.
I was wondering: are you planning to release a theme update soon that adds apiVersion: 3 across all registered blocks?
I’ve attached a quick screenshot/recording of my console so you can see the warnings popping up!
Thanks again for your great support and taking the time to look into this with me.
Best, João
Attached files: Captura de Tela 2026-04-12 às 14.43.31.png
Captura de Tela 2026-04-12 às 14.44.10.png
Gravação de Tela 2026-04-12 às 14.42.27.mp4
Hello João
It looks like WordPress 7.0 will render the editor in an iframe, regardless
https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/
as you can see from the code we are using the default value for the apiVersion parameter
If you like - if you can provide wp admin access with full rights using Plugin File Editor (in a private comment) we can modify the apiVersion for all createBlock function calls.
Thank you.
Clapat Support
Review Envato Item Support Policy
Follow us!
https://www.clapat.com/
https://www.facebook.com/clapat.ro
https://www.instagram.com/clapat.themes/
https://x.com/clapatdesign
https://www.linkedin.com/company/clapatstudio
https://www.tiktok.com/@clapatstudio
Hello João, ok all done, hopefully I got it right.
Thank you.
Clapat Support
Review Envato Item Support Policy
Follow us!
https://www.clapat.com/
https://www.facebook.com/clapat.ro
https://www.instagram.com/clapat.themes/
https://x.com/clapatdesign
https://www.linkedin.com/company/clapatstudio
https://www.tiktok.com/@clapatstudio