いつもお世話になっております。

Cocoonフォーラムの以下スレッドで報告されていたのと同じ事象がXwriteでも確認できました。

・WordPress7.0に向けてのGutenbergエディターの警告について | Cocoonテーマに関する質問 | Cocoon フォーラム

現状、Xwriteの独自ブロックの多くがdeprecatedとなっており、WordPress 7.0以降にアップデート時にブロックエディターの動作不良が生じる可能性があります。

上記ご認識いただき、お早めに新APIへの移行対応をお願いいたします。

▼エラー文

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 "xwrite/xxxxxxx" is registered with API version 2. 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.

▼URL リンク先と参考文

Migrating Blocks for iframe Editor Compatibility – Block Editor Handbook | Developer.WordPress.org（英語）

In WordPress 7.0, the post editor is planned to always work as an iframe, regardless of the apiVersion of registered blocks.

Ahead of this, to encourage developers to test in the iframe editor, WordPress 6.9 introduces the following developer warnings and schema changes:

• Browser console warnings: When blocks are registered with apiVersion 2 or lower, WordPress displays the following message in the browser console:
  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 "my-plugin/my-block" is registered with API version 2. 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.
• block.json schema update: The block.json schema has been updated to only allow apiVersion: 3 for new or updated blocks. Older versions (1 or 2) will no longer pass schema validation.