Hi, I’m on the latest version of Newspaper 12.7.6 and on WordPress 7.0.
All of a sudden i lost the template box that’s inside the gutenberg editor wordpress at the very bottom of the page (under the post copy I mean). Does this have to do with that? https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/
The same template box is inside the theme’s panel settings > Post Settings > Default post template
Tell me if the issue is something you already know and if you’re working on fixing it. Or else we will have to mitigate it internally in our company. Thanks.
Hi,
Those are the post settings. Assuming the post settings are active in the options -> https://prnt.sc/K99tK0XTiXrl they must be somewhere in the post edit screen.
Maybe the post settings section is closed at the bottom -> https://prnt.sc/Nabkz9NfkbDa
Or maybe it was moved by mistake in the sidebar on the right -> https://prnt.sc/omg9rOu4Sc1P
Currently there’s no such issue in the theme. Maybe the post settings section is just in a different location in your post edit screen. But in case it’s truly missing, then it’s very unusual. I can take a look at it if you want, you can send us an email at contact@tagdiv.com and provide a link to the website and admin login. I will check as soon as possible.
In the meantime if you need to use the post settings you could use the classic editor plugin.
Thank you!
“Hello, I am here to report the same issue. Since updating to WordPress 7.0, the Gutenberg editor is severely bugged, very slow, and the layout/styles are completely broken.
I have done some troubleshooting on my end:
I tested other WP 7.0 sites without the Newspaper theme, and the editor works perfectly.
I disabled all third-party plugins, and the issue persists. It is definitively tied to the theme and the tagDiv Composer.
Checking the browser console, there are conflicts with the new WP 7.0 iframe structure. The console throws errors such as: td-guten-blocks-editor-css-css was added to the iframe incorrectly and fails to load load-scripts.php.
Is there an ETA for a full compatibility patch for WordPress 7.0?”
“Chrome Console”
load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-dom-ready,wp-hooks&ver=7.0:5 JQMIGRATE: Migrate is installed, version 3.4.1
v833ccba57c9e4d2798f2e76cebdd09a11778172276447:1 Failed to load resource: net::ERR_ADDRESS_INVALID
deprecated.min.js?ver=990e85f234fee8f7d446:1 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 “mpp/user-profile” 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.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 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 “mpp/user-profile-enhanced” 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.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 wp.compose.withState is deprecated since version 5.8. Please use wp.element.useState instead.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 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 “advads/gblock” 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.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 36px default size for wp.components.SelectControl is deprecated since version 6.8 and will be removed in version 7.1. Note: Set the __next40pxDefaultSize prop to true to start opting into the new default size, which will become the default in a future version.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 36px default size for wp.components.RangeControl is deprecated since version 6.8 and will be removed in version 7.1. Note: Set the __next40pxDefaultSize prop to true to start opting into the new default size, which will become the default in a future version.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 wp.editor.RichTextToolbarButton is deprecated since version 5.3 and will be removed in version 6.2. Please use wp.blockEditor.RichTextToolbarButton instead.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
load-scripts.php:1 Failed to load resource: the server responded with a status of 404 ()
I cant paste the entire console error, since wordfence block me
Yes, I confirm that I see something very simililar in my console tab, especially the last two sections. Have you tried downgrading yet in staging?
Waiting for a response…
Waiting for response 2…
Sorry for the delay.
Despite the deprecation notices (not errors) which we will fix, on our end the block editor from wordpress is working same as before. There are no sever bugs, it’s not very slow, and the layout/styles are not completely broken. We’re simply not experiencing these issues while using the latest wordpress and theme versions. And there’s nothing preventing the full usage of the block editor.
I’m checking tens of websites each day, and I haven’t seen these symptoms so far. There must be something specific happening in some cases most likely.
That’s why it would be best if we could check directly on the website where it’s happening. Please send us an email at contact@tagdiv.com and provide a link to the website and admin login. We will check to try and find out what’s happening there exactly.
Thank you!
I fixed it by adding this in the file: wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php (line 576).
Fix:
add_meta_box($this->id . ‘_metabox’, $this->title, array($this, ‘_setup’), $type, $this->context, $this->priority, array(
‘__block_editor_compatible_meta_box’ => true,
‘__back_compat_meta_box’ => false,
));
I am writing my own version of the theme to wean off third parties.
