Skip Navigation

[Resolved] wysiwyg field not saving when on visual mode

This support ticket is created 3 years, 3 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 10 replies, has 3 voices.

Last updated by davidJ-4 3 years, 2 months ago.

Assisted by: Waqar.

Author
Posts
#2199299

I created a custom post "Streaming" that has a few WYSIWYG fields.

Contents, that was entered in these fields in visual mode, couldn't be published or updated. After saving, the content would just disappear. I had to re-entered the content and save it in text mode to make it work.

In short, I can only publish or update when the WYSWYG fields are on text mode.

#2199443

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

We had a related issue, but it was fixed in Types 3.4.14, which you have installled.

I would suggest you clear the browser cache (I recommend reloading the page with the browser dev tools open on the network tab and the disable cache option set), and see if the problem still occurs.

If so, you are likely affected by the WordPress issue described here: https://toolset.com/errata/visual-tab-of-wysiwyg-fields-may-not-initialize-correctly-appear-not-to-save-data/

Until that is fixed, you may want to try using the enable jquery migration helper plugin as a workaround, as described in the erratum.

#2205459

Hi Nigel.

Thank you for your response.

I have cleared the cache and the problem persist. The workaround solution isn't working either.

Please advice on what I should do next. I will still enter content through the text mode since it seems to be working.

#2205673

Thanks for writing back.

Can you please share temporary admin login details, along with the link to an example page where this issue with the WYSIWYG field can be seen?

I'll also need your permission to download a clone/snapshot of the website, in case, it needs to be investigated on a different server.

Note: Your next reply will be private and it is recommended to make a complete backup copy, before sharing the access details.

#2212829

Thank you for sharing the admin access, but, I keep getting blocked by the Wordfence plugin.
( Your access to this site has been temporarily limited by the site owner )

Can you please make sure that the username and the password are correct and there are GEO IP restrictions enabled? The username and the password that you shared earlier were the same, which doesn't seem right.

I'm setting your next reply as private again.

#2215381

Thank you for sharing the admin access and I've downloaded the duplicator package from your website.

I'll keep you updated with the findings and thank you for your patience.

#2216333

Thank you Waqar.

I will activate our ftp security back on again.

#2217377

Thank you for waiting.

During testing on your website's clone, I noticed that I was not able to save the content in the first WYSIWYG field "Synopsis", in the visual tab. In other WYSIWYG fields, the content got saved correctly.

I turned on the "Editor" option in the "Streams" post type settings ( screenshot: hidden link ) and then cleared all involved caches. After that, I was able to save the content in the "Synopsis" field too, while using the visual tab.

Can you please follow the same steps on your website too and see if it works?

regards,
Waqar

#2222647

Sorry for the late reply.

I did as you instructed and it is working.

Thought I notice that the html is stripped and does not recognize enter and paragraph on the front-end

Thanks

#2223783

Thanks for the update and glad that it worked.

As you're using the Divi builder's dynamic source feature, it seems to be responsible for removing the HTML from the WYSIWYG field's output.

If you'll disable the dynamic source from the text module and instead, use Toolset Fields API shortcode, it will show the content correctly:
( ref: https://toolset.com/documentation/customizing-sites-using-php/functions/#wysiwyg )

For example:


[types field="synopsys"][/types]

#2223955

My issue is resolved now. Thank you so much for your help. I used [wpv-autop][/wpv-autop] to fix the html because I still wanted to use the Divi dynamic source.