I am trying to: Have a pattern for a book layout. Insert this into a post. The pattern has a core image, heading, text and button block. Once intered have been using dynamic data to link to Toolset CPT / Fields.
Seeing two issues.
Not letting me activate the Dynamic data source
If I refresh page get block errors and hav eto recover blocks
Thanks Nigel. Just an update. I am now getting white screen on regular posts that had dynamic blocks. That wasn't happening before. May be from the core big update yesterday.
Which core blocks? We know about the problem with dynamic sources and the core image block, but we don't have confirmation of any other core blocks being affected.
If you have the same problem with pages that don't use the core image block please let me know.
I'm hoping for an update from the developers soon about that.
Hi Nigel. I don't know how much of the issue is being caused by the new block bindings API, but this PR is something the Toolset developers should probably be aware of if they aren't already. hidden link
I'll share that with the developers when I meet with them this morning.
The original issue isn't actually related to the Block Bindings API, it is connected with changes to certain blocks with text fields that switched to rich text fields. They finally have a fix, it is being tested before being released, which should be very soon.
Thanks Nigel. I will add some additional checks to our WordPress update verification checklist to more fully test Toolset features. We usually start with the second beta release, so will try and feedback anything we see that might have impact. I know it is hard the way the core team is introducing breaking changes without lots of discussion ahead of time.
We shared a pre-release version with a proposed fix but we've had some feedback about it not working, and we are identifying why in those particular cases, so the fix is not ready to be released yet, I'm afraid.
For now, the advice remains to hold off from updating to WordPress 6.5.
Good morning. Just checking to see if any visibility to resolution on the issue yet. We tried a rollback on WordPress but it caused some other issues. Thanks so much.