Nigel
Supporter
Languages:
English (English )
Spanish (Español )
Timezone:
Europe/London (GMT+00:00)
Luis, I just wanted to let you know that one of the developers is currently working on this, so we should hopefully have a solution before too long.
I'll keep you posted.
Thanks, Nigel.
Let´s hope that this solution comes soon.
Nigel
Supporter
Languages:
English (English )
Spanish (Español )
Timezone:
Europe/London (GMT+00:00)
This is proving quite challenging, the changes introduced in WordPress 5.9 that affect the Media and Text block are difficult to adapt to without a significant update to dynamic sources.
The developers are still working on this but don't have a fix at the moment. They added an erratum in the meantime: https://toolset.com/errata/core-wordpress-media-and-text-block-broken-when-using-toolset-dynamic-sources/
Again, we'll let you know when they report some actual progress.
Hi. Any news on this?
This issue is almost a year and a half old.
Since this issue happens when shaving the content template, I have to do all kind of complicated things to try and complete a project on which I´ve already spent many many hours, and for which a couple of years ago I had chosen to use Toolset (not a too wise decision, I´m afraid). Things like copying the content of a content template post from the database, then editing the html by hand and then pasting it back on the database record, because I just can´t use the WP block editor to do any modification to my content template. Very, very annoying and time-consuming, as well as a possible source for unwanted errors, as you can imagine.
Nigel
Supporter
Languages:
English (English )
Spanish (Español )
Timezone:
Europe/London (GMT+00:00)
I'm sorry there hasn't been any progress, it is on the development board, but we cannot determine the order in which the developers take tickets to work on. With only a single customer report about this, and as there are workarounds available involving Column and Container blocks to replicate the functionality of the Media and Text block, it seems the developers are prioritising other issues.
I have once more commented on the internal ticket, drawing attention to how long this issue has been open.
As soon as there is any progress the erratum will be updated.
Once again, I'm sorry that I don't have a solution to provide you.
