WYSIWYG markup not applied

This thread is resolved. Here is a description of the problem and solution.

Problem:
HTML markup added to WYSIWYG fields is not applied when rendering the fields in the front end.

Solution:
Wrap the fields (when inserting as shortcodes) in the wpv-autop shortcode.

Relevant Documentation:
https://toolset.com/errata/paragraph-tag-is-stripped-in-wysiwyg-loop-items-and-page-builders-generated-content/

This support ticket is created 4 years, 9 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
-	-	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00
-	-	-	-	-	-	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: How to build a site with Toolset

This topic contains 4 replies, has 2 voices.

Last updated by Daniella 4 years, 9 months ago.

Assisted by: Beda.

Author

Posts

February 21, 2020 at 4:10 pm #1521371

Daniella

For some reason the content in the WYSIWIG custom field is not rendering on my site running the latest Generate Press theme. Don't appear to have any other styling issues, just this.

Please see vid hidden link

Is it a Toolset setting, or do I need to troubleshoot with the theme?

Thanks!

February 22, 2020 at 9:35 am #1522317

Beda

This should be due to the problem mentioned here:
https://toolset.com/errata/paragraph-tag-is-stripped-in-wysiwyg-loop-items-and-page-builders-generated-content/

This happens often, please try to use [wpv-autop] shortcodes around the WYSIWYG Field when you output it.

February 24, 2020 at 4:59 pm #1525459

Daniella

Beda,

Thanks, that worked. Once the bu is resolve, will [wpv-autop] cause issues? Also, the link you passed along mentioned DIVI. We are not using any page builders ... Toolset Blocks is the page builder 🙂

Best.

February 25, 2020 at 8:40 am #1526527

Beda

It could over-p it, yes, if it gets resolved, but I do not think this will happen anytime in the imminent future.
The problem here is that at some point you reach a limit of ability to guess whether or not content should or should not be autop'd

If that erratum gets resolved, I believe it will be because we would deliver a whole new rendering mechanism.

This issue is not due to Divi or only to Divi, it is basically an issue with content rendering in WordPress generally, when the content passes thru several content filters (nested sometimes).

February 25, 2020 at 11:15 am #1526801

Daniella

My issue is resolved now. Thank you!