Skip Navigation

[Resolved] Paragraph/Line breaks missing from custom fields

This support ticket is created 2 years, 4 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
- 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/Karachi (GMT+05:00)

This topic contains 2 replies, has 2 voices.

Last updated by Waqar 2 years, 4 months ago.

Assisted by: Waqar.

Author
Posts
#2420093

Our client is reporting that all of their custom WYSIWYG fields are missing any paragraph or line breaks. All of the text is lumped together in all of the custom fields.

We recently updated to Version 3.4.16.

#2420427

Hi,

Thank you for contacting us and I'd be happy to assist.

To troubleshoot this, I'll need to see how these WYSIWYG fields are being used in the back end.

Can you please share temporary admin login details, along with the link to an example page?

Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.

regards,
Waqar

#2421549

Thank you for sharing these details.

If you'll check the content of the WYSIWYG field "Content" in the edit screen of this "Government, Regulatory, and Internal Investigations" 'Practice' post, you'll see that the text is added as a one-long paragraph, which is how it is showing on the front end too.
( screenshot: hidden link )

Whereas, if you'll check the content of the same field in another 'Practice' post "White Collar", you'll see that the formatting and styling information is there in the back end, which is why the same is also showing on the front end.
( screenshot: hidden link )

This means that there is nothing wrong with the display logic of your code used in the theme's template file to get and show this content. You'll just have to make sure that the necessary formatting and paragraphs are added to the field's content itself. You can check how the same field's content in the same post is set in the older staging version of the website to confirm this.

Note: Some improvements were added around the handling of the WYSIWYG field's content in the latest Types 3.4.16 release, but those changes, shouldn't remove the paragraph and formatting information from the existing field's content.
( ref: https://toolset.com/download/toolset-types/#changelog )