Skip Navigation

[Resolved] Rogue p tags and linebreaks in layout

This support ticket is created 6 years, 8 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/Hong_Kong (GMT+08:00)

This topic contains 4 replies, has 2 voices.

Last updated by jonathanB-16 6 years, 8 months ago.

Assisted by: Luo Yang.

Author
Posts
#887022
Screen Shot 2018-05-15 at 4.30.34 pm.png
Screen Shot 2018-05-15 at 4.29.31 pm.png

Hello, I am trying to update to the latest version of layouts, and I have done the updates on my test site but the new version has created all of this rogue spacing in the product layout.

Link to a page where the issue can be seen:

hidden link

In the screenshots you will see how it is supposed to look (without the rogue white space), and what it looks like after updating.

#887031

Hello,

I have tried the credentials you provided above, it is not valid, I get this error message:
ERROR: Invalid username.

Please check it, make sure it is a valid admin account.

#887034

Apologies, this has now been fixed.

#887189

Thanks for the details, I can login your website, and see the problem you mentioned above, here is what I found:
1) It seems to be a issue of Visual editor cell,
hidden link
the visual editor cell in the right.

2) currently, you can replace it with Content template cell with same codes, it should be able to fix the problem, can you confirm it?
https://toolset.com/documentation/user-guides/content-template-cell/

3) I am downloading the database dump file from your website, try to duplicate the same problem, will update this thread if there is anything found

#891233

I can confirm that this workaround has worked. Thanks.