[Resolved] Another issue with core blocks and dynamic data

[Author]

Posts

[John]

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

Link to a page where the issue can be seen:

hidden link

I expected to see:

Instead, I got:

[Nigel]

Hi John

What you are describing seems to be a side effect of this existing issue: https://toolset.com/errata/wordpress-6-5-update-breaks-editor-if-using-core-media-block-with-dynamic-sources/

When I tried what you described I got the same JS errors in the console as reported in the above.

The developers are actively focused on fixing this and a related issue right now, so I'm hopeful we'll have a fix before too long.

I'll escalate this and attach it to the same internal ticket so I can advise you when we have a fix.

[John]

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.

[John]

Nigel, just a quick update. I am now having an issue editing regular posts that have core blocks with dynamic data. This wasn't happening before.

[Nigel]

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.

[John]

This one also involved image block. I will test one with a just a text block to confirm

[John]

Nigel, I added a post and then just tried to turn on dynamic data for a text block. It won't let me activate.

[Nigel]

You're right. It hasn't been brought up so far, but I just tested the Paragraph block and it suffers the same problem.

The error is the same, though, and so it should come under the same umbrella as the other reports.

As soon as I have a solution from the developers I'll share it with you.

[John]

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

[Nigel]

Thanks John

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.

[John]

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.

[John]

Hi Nigel. Just checking in. Any update on this one?

[Nigel]

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.

[John]

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.

[Nigel]

Sorry for the continuing wait. I speak to the developers most days and they said they expect the solution to be ready to publish early next week.

I will update you as soon as it is published.