I recently opened a backend page built with Toolset blocks. Instead of seeing the visual code (blocks, etc.), there is only a message 'view not found'. And the right sidebar, which contains normally the settings of the selected block does not contain any information. But in the frontend, everything is working fine at the moment.
After some internet searches, I conclude, that Toolset is not anymore compatible with the new version of WordPress, due to API-problems, is that true? For a fast solution, I cannot downgrade the WordPress version.
So do you provide a patch for this problem? At the moment, I cannot edit our views built in block editor, a very bad situation.
I add below all messages in the console after refreshing a backend page with a block view.
kind regards
Franz
Hi Franz,
We do not have reports of incompatibility with WordPress 7.1.3. But if that is the case, we will investigate on your website.
Would you please provide the copy/staging version login information for your website so we can check?
Thanks.
Hi Amirian,
thanks for your fast response. Finally we found, that this issue is caused by a restrict plugin, which does not only restrict a page but also the views in the backend of this page... strange behavior.
BUT: when working on this issue, we found the following message in the console alfter loading a backend page containing a toolset block view:
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 "toolset-views/custom-search-reset" 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. deprecated.min.js:3:1139
This is not yet a mistake, but a warning. It seems that toolset uses API version 1, but in future, WordPress will work with API version 3. So my question is: will toolset fill the gap by providing API version 3 in the code? Is there a timetable for that?
Kind regards
franz
Hi Franz,
Yes, we will replace deprecated functionality with newer versions when the time comes. Our development team actively works on these scenarios, and we will release new versions as the improvements become available, depending on the WordPress version.
Thanks.
many thanks für your support
