[Resolved] paragraph tag inserted despite “Manual paragraphs” setting

[Author]

Posts

[ABSTRACTUS]

In a Content Template, I have included the following call:
<p> …
[wpv-if info="wpcf-exhibition_opening_info" evaluate="!empty($info)"]<br /><span style="color:rgb(0, 0, 0); font-family:lucida grande,tahoma,verdana,arial,sans-serif; font-size:12px; line-height:normal; text-align:-webkit-auto">[types field="exhibition_opening_info" class="" style=""][/types]</span>[/wpv-if]</p>

Although the setting is on Manual paragraphs, the output source code on hidden link includes a <p> tag after the <span>:
<p> …
<span style="color:rgb(0, 0, 0); font-family:lucida grande,tahoma,verdana,arial,sans-serif; font-size:12px; line-height:normal; text-align:-webkit-auto"><p>Speed Speech von Iris Ganz, Performancekünstlerin</p>
</span></p>

As a result, the formatting defined in the <span> is now overridden by the <p> formatting and therefore got useless.

How can I prevent Views from inserting this <p> tag? I have set the Template to "Manual paragraphs", so imho that should be the solution, but obviously it is not :-S

Thank you for any idea!

[Shane]

Hello,

Thank you for contacting our support forum.

The reason why this is happening could be because you are using older versions of our plugins.

Could you update them and let me know if this issue still remains?

Thanks,
Shane

[ABSTRACTUS]

Hi Shane,
Thank you, yes the issue remains also after updating the plugins and emptying the cache.
Claudius

[Shane]

Hi Claudius,

What you can do is to add the wp-noautop shortcode and this should help.

Have a look here.
https://toolset.com/documentation/user-guides/views-shortcodes/#vf-310704

Thanks,
Shane

[ABSTRACTUS]

Hi Shane,

Thank you for the hint. The shortcode looks promising – but doesn't help :-S

I have wrapped the whole Content Template code with [wpv-noautop][/wpv-noautop] and cleared/switched off all caches – but the <p>'s are still in the code…

Do you have any other idea?
Thank you, Claudius

[Shane]

Hi Claudius,

Would you mind allowing me to have admin access to the site so that I can have a look at this for you ?

The private fields will be enabled for your next response.

Thanks,
Shane

[Shane]

Hi Claudius,

Thank I was able to log in but i'm struggling to find the template that you are having the issue with.

Could you send me a link to the template on the backend ?

Thanks,
Shane

[ABSTRACTUS]

Sure, sorry i forgot to indicate.
It is the Embedded Opening for Newsletter template
hidden link
Embedded in the Upcoming Openings Dynamic by ArtRegion for Newsletter view hidden link

[Shane]

Hi Claudius,

Thank you, I checked this for you and on the frontend. There isn't any auto paragraphs being added.

Even so I suspect that this is a case where your view is made much more complex than it needs to be. I'm not sure why you are calling a post body template on a view that is not attached to the view at all.

Then in that template again you are calling the same post body with a completely different content template. I would suggest doing some cleanup of your code to ensure that it is streamline.

Thanks,
Shane

[ABSTRACTUS]

Hi Shane

Thank you for the cleanup hints – in fact, I've used content templates instead of putting the code directly in the view because I intended to reuse the content template "snippet". But I'll have a look at it for sure.

Regarding the <p> inserted, whether it's called "auto" or some differently, I cannot help myself: When I call the source code of the page hidden link I still have the <p>'s in there that override my formatting for the "exhibition_opening_info" field. And my question remains, how can I get rid of them resp. format the text differently than <p> style?

Thank you,
Claudius

[Shane]

Hi Claudius,

Instead of wrapping the entire section in the wpv-noautop shortcode. Just wrap this section only where you are having the issue.

So it should be <span>[wpv-noautop][types field='my-field'][/types][/wpv-noautop]</span>

Thanks,
Shane

[ABSTRACTUS]

Hi Shane

Also at the recommended position, the [wpv-noautop] didn't help, the <p> was still there.

But I found the solution: adding output="raw" to the [types field='my-field'] shortcode eliminated the wrapping <p>!

Thank you for your ideas and inputs anyway!
Claudius