Skip Navigation

[Resolved] Some fields aren't saved

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 – 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, 1 month ago.

Assisted by: Shane.

Author
Posts
#2207721

I am trying to:
Update a post but the WYSIWYG fields "Description du poste" and "Qualification" aren't saved

Link to a page where the issue can be seen:
hidden link

I expected to see:
The fields saved

Instead, I got:
Fields empty

#2208131

Shane
Supporter

Languages: English (English )

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

Hi Matthias,

Thank you for getting in touch.

We are actually aware of this issue and have set up an erratas page for it.
https://toolset.com/errata/visual-tab-of-wysiwyg-fields-may-not-initialize-correctly-appear-not-to-save-data/

Unfortunately the only workaround seems to be to store your content using the text tab.

Thanks,
Shane

#2210955

Hello, I followed this workaround and it resolved my problem:

Comments on the WP tickets suggest that using the jQuery migrate helper plugin and choosing the legacy jQuery version can “fix” the issue: https://wordpress.org/plugins/enable-jquery-migrate-helper

Thank you for giving me the link to the "erratas page".
Could you let me know when the issue is resolved so that I deactivate the plugin ?

Wishing you the best,
Mat

#2210963

Shane
Supporter

Languages: English (English )

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

Hi Matthias,

Thank you for sharing your solution with us.

We will let you know once this has been resolved.

However it should be noted that a likely fix will be coming from wordpress core itself and not from us.

Thanks,
Shane