Skip Navigation

[Resolved] WYSIWYG Saving issues

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
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10: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/Kolkata (GMT+05:30)

This topic contains 5 replies, has 2 voices.

Last updated by Minesh 2 years, 11 months ago.

Assisted by: Minesh.

Author
Posts
#2250557

The issue here:
https://toolset.com/errata/content-of-wysiwyg-field-lost-when-updating-posts/

Still occurs on site using 3.4.15. Please advise.

Tell us what you are trying to do?
Save from editor visual tab.

Is there any documentation that you are following?
https://toolset.com/errata/content-of-wysiwyg-field-lost-when-updating-posts/

Is there a similar example that we can see?

What is the link to your site?
hidden link

Post Type:
Jobs

Custom Field:
Job Description

I created a test field called TEMP to test on.

This is a big issue, please advise.

#2250561

I edited the login information as I think this is not a private ticket, but public. Please contact me for login credentials.

Thanks.

#2250625

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

Yes, please, Can you please share admin access details as well as mention the required steps we should follow that should lead us to reproduce the issue.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#2252135

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I checked on your install and yes I can see the issue.

But the strange this is that I could not able to reproduce the issue when I checked with clean WordPress site. I just try to install a clean WordPress install and I only install and activated Types plugins.
- I've created the post type Student and I disable the post content (editor) field on this post type
- I've created custom field group and added WYSIWYG field and assigned this custom field group to post type "Student"
- I've tried to add new post and (where there is no content field available) I see only the WYSIWYG field is available and I tried to add content and saved the post and it works just fine.

I see you are using number of third-party plugins including the "Classic Editor" plugin. In order to minimize the cause of the issue and to ensure there is no conflict between third-party plugins or theme:
*** Please make a FULL BACKUP of your database and website.***
Could you please try to resolve your issue by deactivating all third-party plugins as well as with the default theme to check for any possible conflicts with any of the plugins or themes? - Do you see any difference?

#2254445

Hi. I went thorough the plugins and found that two plugins cause the post not to update in the editor:

Advanced Custom Field's Pro
FontAwesome

If any of these two plugins are active, the post update will not work.

Thanks.

#2254517

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

As when only Toolset plugins active I do not reproduce the issue and even you shared the update that the issue is when you activate the plugins:
- Advanced Custom Field's Pro
- FontAwesome

Can you please check with the plugin author of "Advanced Custom Field's Pro" and "FontAwesome" to ensure that the issue is from their side or Toolset. If they share that the issue is from Toolset, we are happy to address it.