-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update theme for WordPress 5.8 - widget block editor and theme.json #6
Comments
I've reproduced the Widget block editor problem I'll attempt to follow the recovery steps deleting one widget at a time until it gets better. Below is the response from https://s.b/wp-pompey/wp-json/wp/v2/sidebars?per_page=100&_locale=user
|
I was able to reproduce the problem by adding the Legacy widget and choosing Meta again. |
The error log shows
|
Updating Jetpack to v10.0.0, released yesterday, appears to resolve the Fatal Error problem. |
There was also a problem with the site logo when it was used in the |
v0.1.1 is now installed on wp-pompey.org.uk. In the Site Info sidebar the WordPress Info block is repeated. |
WordPress 5.8 was released on 20th July 2021.
The WordPress Portsmouth Online Meetup on the 21st was "What's new in WordPress 5.8 and how to use it".
The theme needed to be updated to:
I made the changes on the fly. These need to be formally implemented.
Bugs to be investigated
During the preparation and the Live demo I encountered a number of problems which we didn't satisfactorily resolve.
These need to be investigated.
They may not be anything to do with the theme, but I'll use this issue to record them.
They can be reassigned when the true source of the problem has been identified.
The demo was recorded so we have evidence to share.
Bugs noted:
Jetpack messages
See the slide deck.
2. Widget block editor
Console messages
block-serialization-default-parser.min.js?ver=2fc6dec19af6d4c5e5fec8f6fdc1a10b:2
Uncaught (in promise) TypeError: Cannot read property 'length' of null
at a (block-serialization-default-parser.min.js?ver=2fc6dec19af6d4c5e5fec8f6fdc1a10b:2)
at p (block-serialization-default-parser.min.js?ver=2fc6dec19af6d4c5e5fec8f6fdc1a10b:2)
at f (block-serialization-default-parser.min.js?ver=2fc6dec19af6d4c5e5fec8f6fdc1a10b:2)
at Ar (blocks.min.js?ver=e2b6602c7ebbe8ce93832ce35d81be1c:2)
at T (edit-widgets.min.js?ver=4c0c32581bede8cfef25865f0e87b861:2)
at Object.q [as fulfill] (edit-widgets.min.js?ver=4c0c32581bede8cfef25865f0e87b861:2)
at q.next ()
at redux-routine.min.js?ver=7f20dbcdb5d5645c977063e356eb95cf:2
at redux-routine.min.js?ver=7f20dbcdb5d5645c977063e356eb95cf:2
at redux-routine.min.js?ver=7f20dbcdb5d5645c977063e356eb95cf:2
The text was updated successfully, but these errors were encountered: