This thread is resolved. Here is a description of the problem and solution.
Problem:
Remove spaces from legacy post view.
Solution:
You can edit the post view, in section "Loop Editor", remove all line breaks, merge all codes in one single line, and test again.
Relevant Documentation:
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 5 replies, has 2 voices.
Last updated by 2 years, 9 months ago.
Assisted by: Luo Yang.
I have a view team-sgt-name-role I've created using custom Term Fields and the view uses a taxonomy term filter so I only have one termmeta match.
[types termmeta="team-role-type"][/types], [types termmeta="team-role-contact-name"][/types]
Very simple.
In my page where I use the view in the backend it all looks fine in the Visual View.... (see image). I added a comma at the end of the view: [wpv-view name="team-sgt-name-role"], in my Page and adding the comma highlights the issue. When in the front end it adds the extra space before the comma (see image Front End Output with red square highlighting extra space before comma).
I've checked there are no spaces in the view, and I think if there were it would show up in the block on the page (i.e. in the image Visual View - but as you can see this is correct).
