Skip Navigation

[Resolved] WYSIWYG field don't save data

This support ticket is created 2 years, 12 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 – 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 2 years, 12 months ago.

Assisted by: Shane.

Author
Posts
#2268641
Captura de pantalla 2022-01-17 193535.jpg

Hi,
I've a custom field WYSIWYG but when I update the post the data in this field is lost. The other fields are saved correctly.

Additional information:
in the CPT "sections to display when editing" the editor is disabled as I show you in the attached screenshot.
If I enable this option, a new editor appears in the post and BOTH WYSIWYG editors save the data, but I want to use ONLY the custom field.

thanks,
David

#2268777

Shane
Supporter

Languages: English (English )

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

Hi David,

Thank you for getting in touch.

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

Unfortunately we don't have a solution for this one as the fix will need to come from the wordpress core itself. You can workaround the issue by using the Multiple line Custom Field or the use of the default content area.

Thanks,
Shane

#2271177

Is there some timing to get a solution? my project is not viable with this problem.

thanks
David

#2271397

Shane
Supporter

Languages: English (English )

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

Hi David,

Unfortunately not, at this point the most we can do is to wait on a solution from wordpress core itself for this to be fully resolved.

Thanks,
Shane