[Resolved] Cannot save or edit content in some of the custom fields

[Author]

Posts

[nigelF-3]

When I create new custom posts and I save as drafts or try to publish the content I have just added is wiped out of several fields. I have found also that when I try to edit some of these same fields in an existing post the changes do not get saved.
I have not seen this issue before, but I also haven't created or edited any of my custom posts for a while.
The affected fields are in my Products custom category and are called "description" and "specifications".
An example of a new item is at this URL: hidden link

I have provided below the debug info from the site, an admin account you can use and also a link to a duplicator backup I have just taken.
You can use the same admin account to login to the duplicator backup and the live site.

I have to create some new custom posts for public release on Wednesday this week (11/27/21) so I would appreciate your help as soon as possible.

[Minesh]

Hello. Thank you for contacting the Toolset support.

We have following known issues related to WYSIWYG field when its saved the content is lost.

Can you please try to follow the workaround offered with the following errata and try to resolve your issue:
=> https://toolset.com/errata/content-of-wysiwyg-field-lost-when-updating-posts/
=> https://toolset.com/errata/visual-tab-of-wysiwyg-fields-may-not-initialize-correctly-appear-not-to-save-data/

[nigelF-3]

Hello Minesh,

Thanks for getting back to me with the workaround hints.

This does indeed work and I can now get on with my project.
However, it's not ideal as the whole idea of the WYSIWYG fields is that we can see what we are going to get rather than having to write code.

How and when will we be told when the issue has been fixed?

Best wishes,
Nigel

[Minesh]

As you can see its already mentioned with our errata that:
=> https://toolset.com/errata/visual-tab-of-wysiwyg-fields-may-not-initialize-correctly-appear-not-to-save-data/

It is reported to WP core several times (https://core.trac.wordpress.org/ticket/52111, https://core.trac.wordpress.org/ticket/52133, https://core.trac.wordpress.org/ticket/53644 is still open).

We await confirmation that the issue is fixed in WP.

So, you will have to wait until its get fixed from WordPress itself.

[nigelF-3]

My issue is resolved now. Thank you!