Skip Navigation

[Resolved] WYSIWYG Fields not saving

This support ticket is created 3 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 3 replies, has 2 voices.

Last updated by Shane 3 years ago.

Assisted by: Shane.

Author
Posts
#2246281

I am trying to: Create new post within Custom Post Type

Link to a page where the issue can be seen:

I expected to see:

Instead, I got: None of the WYSIWYG fields are saving after publishing a new post. All other fields are working properly. It only appears to be happening in one of our custom post types. After publishing, the WYSIWYG fields are blank. If I duplicate a previous post and try to update the fields, they revert back to the original content after publishing.

#2246307

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hello,

Thank you for getting in touch.

I suspect the issue that you're currently experiencing is the same as the one in the link beow.
https://toolset.com/errata/visual-tab-of-wysiwyg-fields-may-not-initialize-correctly-appear-not-to-save-data/

Unfortunately this is something that is out of our hands and will require a fix from the wordpress team itself in order to fully resolve.

Thanks,
Shane

#2246311

Sounds similar, but not the same. Even when switching to the Text tab, there is no content. Content is also not being published on the front end.

#2246355

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hello,

Essentially both issues are one in the same given the nature, we also have customers reporting that even in the text tab the problem still persist.

So there isn't much we can do until wordpress core fixes this.

Thanks,
Shane