Skip Navigation

[Resolved] Data getting removed from WYSIWYG after changing custom categories

This support ticket is created 3 years, 2 months 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 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 4 replies, has 3 voices.

Last updated by Waqar 2 years, 6 months ago.

Assisted by: Waqar.

Author
Posts
#2183163

LCR

The bug where the content in WYSIWYG is not saving was a previous bug that seemed to come up again after the update provided to fix the issue. It appears to be still happening on other websites. (Plugin Version 3.4.14)

#2183385

Hello,

We've recently discovered and highlighted this issue that if the "Editor" option is disabled for a post type, any WYSIWYG field attached to that post type can't save the changes in the 'visual' tab, properly.

I don't have a time estimate to share at the moment, but, I'll keep you updated on the progress through this ticket.

Currently, please try these:
Edit your custom post type, in section "Sections to display when editing", enable option "Editor", see screenshot:
hidden link

And test again.

#2186931

LCR

Thank you, the workaround works for now but I'll look forward to an update.

#2187413

Glad that the workaround works and we'll keep you updated on the progress through this ticket.

#2369335

I would like to inform you that the latest Toolset Types plugin (version 3.4.16) is released and contains the fix for this issue.
( ref: https://toolset.com/download/toolset-types/#changelog )

Please update all the Toolset plugins to the latest versions and let us know in case the issue persists.