[Resolved] Auto-paragraphs and wpv-autop shortcode not working with some wysiwyg fields
This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the user was getting auto paragraphs added to their field content even though auto paragraph is disabled in their content template.
Solution:
A way to resolve this is by outputting the raw data from the database.
To do this add output='raw' to your types shortcode.
Example
[types field="things-to-note" output='raw'][/types]
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.
I am trying to:
I have a content template that's displaying a mixture of wysiwyg, number, date and text fields among others for approximately 30+ custom posts.
The majority of posts are fine, though one of the wysiwyg fields in 4 of the posts aren't displaying correctly — no line breaks are being added. It's the same wysiwyg field every time.
When comparing a good post against one that's not displaying correctly, the wysiwyg text is formatted identically in both text and visual modes of the wysiwyg editor.
Replacing the non-working wysiwyg text with the text from the working post makes no difference; line breaks are still not added.
I've tried turning on/off insert auto-paragraphs & wrapping the field in [wpv-auto][/wpv-auto] — no combination of those two solutions makes any difference.
Link to a page where the issue can be seen: hidden link
Under the "Good to Know" tab part way down the page.
Here's an example of an itinerary where the Good to Know content is properly formatted: hidden link
Yes I'm using a content template & yes I tried both enabling and disabling auto paragraphs. Also tried with and without [wpv-autop] around the wysiwyg field in the content template.
fyi the original view shortcode was using the curly braces but I tried using square brackets to see if that would somehow make a difference. It didn't so I just left the square brackets there, in case you're wondering why other shortcodes in the screenshot have curly ones.
