Block apiVersion | WordPress.org

Resolved lofesa
(@lofesa)

4 days, 10 hours ago

Hi.

In the dev tools console panel there are some warnings about the apiVersion in some of your blocks.

For example:

Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “ultimate-post/row” is registered with API version 1. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set the apiVersion field to 3 and test the block inside the iframe editor.

Viewing 2 replies - 1 through 2 (of 2 total)

Thread Starter lofesa
(@lofesa)

4 days, 9 hours ago

Sorry, I forgot this one too. Maybe related to the issue in the 1st post:

ultp-blocks-editor-css-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.<link id=”ultp-blocks-editor-css-css” rel=”stylesheet” href=”https://desarrollo.inter…ks.editor.css?ver=5.0.22” media=”all”>

ultp-style-css was added to the iframe incorrectly. Please use block.json or enqueue_block_assets to add styles to the iframe.<link id=”ultp-style-css” rel=”stylesheet” href=”https://desarrollo.inter…style.min.css?ver=5.0.22” media=”all”>
Plugin Support Razibul Hasan
(@razibulhasan)

4 days, 6 hours ago
Hi @lofesa ,

Thank you for reporting this.

Our development team is already working on updating the Row block to API version 3. The fix will be included in next week’s plugin release.

We appreciate your feedback and patience.
- This reply was modified 4 days, 6 hours ago by Razibul Hasan.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

2 replies
2 participants
Last reply from: Razibul Hasan
Last activity: 4 days, 6 hours ago
Status: resolved