Skip Navigation

[Resolved] Enters aren't displayed in WYSIWYG field anymore

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.

This topic contains 4 replies, has 2 voices.

Last updated by Marcel 1 year, 10 months ago.

Assisted by: Christopher Amirian.

Author
Posts
#2553557

Hi,

This is a WooCommerce site which uses a custom WYSIWYG field. The enters (paragraphs) in that field don't work anymore. See this video: hidden link

Disabling all third-party plugins (except for WooCommerce of course) doesn't fix the problem.

#2553613

Christopher Amirian
Supporter

Languages: English (English )

Hi there,

WordPress has a feature that causes the paragraphs to be stripped out:

https://developer.wordpress.org/reference/functions/wpautop/

Would you please make sure that such a function is not used on your child theme?

You can test by:

- IMPORTANT STEP! Create a backup of your website.
- Switch to the default theme such as "TwentyTwenty" by going to "WordPress Dashboard > Appearance > themes".
- See if the issue is fixed.

The only other thing that I see in our reports is this:

https://toolset.com/errata/paragraphs-and-line-breaks-missing-from-product-description-when-using-product-tabs-block/

It is for product tabs, but worth to try the workaround and seeing the result.

Thanks.

#2553697

Hi Christopher,

I'm using the Divi theme, no childtheme or custom code.

#2554251

Christopher Amirian
Supporter

Languages: English (English )

Hi there,

I understand but I will urge to follow the steps to see if there is a conflict or not. Also I asked about the other solution that you try.

I need an answer about the result of the steps I mentioned tp be able to continue the troubleshooting.

#2558607

After some more experimenting, I've found that the default WooCommerce product description field doesn't have this problem so I used that.

Asking users to switch to the default theme on a live website - and having to build a content template as well - is not the support level I'm used to from Toolset...