How to make a second custom field appear on a new line

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

Problem:

How to make a second custom field appear on a new line, as opposed to a new paragraph, when I use the Fields and Text option?

Solution:

You can use the wpv-autop to wrap those shortcodes, for example:

https://toolset.com/forums/topic/how-to-make-a-second-custom-field-appear-on-a-new-line/#post-2021713

Relevant Documentation:

This support ticket is created 3 years 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.

This topic is split from https://toolset.com/forums/topic/using-toolset-with-divi-theme-builder-for-cpt-and-cpt-archive-templates/

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/Hong_Kong (GMT+08:00)

This topic contains 2 replies, has 2 voices.

Last updated by richard-mazzafroM 3 years ago.

Assisted by: Luo Yang.

Author

Posts

April 15, 2021 at 3:11 am #2021571

richard-mazzafroM

Got it, thank you Luo. I was reading that as the theme itself was missing the archive page. I do have one more question, how to make a second custom field appear on a new line, as opposed to a new paragraph, when I use the Fields and Text option? I tried shift-return and also manually entering <br /> in HTML mode but neither seem to work... They seem to be automatically separated with <p> tags with no way to change that.

April 15, 2021 at 6:58 am #2021713

Luo Yang

Hello,

Thanks for the feedback, it is a known issue, see similar thread here:
https://toolset.com/forums/topic/fields-and-text-block-inserts-field-with-no-formatting/

We decided to not fix this. The current outcome is how WordPress handles paragraphs with only a shortcode. You will get the same output with the core Classic / HTML block. To "fix" this core behavior would mean some ugly filtering, which probably opens new issues for other cases - so we decided to keep it as it is.

You can try the workaround mentioned in above thread, use the wpv-autop to wrap those shortcodes, for example:

[wpv-autop]
...
[wpv-post-link]
[wpv-post-title]
...
[/wpv-autop]

More help:
https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-autop
This shortcode enables the auto-paragraph feature for content placed within it.

April 17, 2021 at 2:08 pm #2024241

richard-mazzafroM

My issue is resolved now. Thank you!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.