This thread is resolved. Here is a description of the problem and solution.
Problem: It looks like there is an error in the code produced by the Loop Wizard for a multi-column grid or table. The syntax highlighter shows an error, and it looks like there is an extra closing div.
Solution: The syntax error here is actually a false reading, because of the way loop output works with rows and columns. It looks like there are extra closing divs because the first column always opens the row, but then the row may be closed in the pad-last item, or in the other index item.
Relevant Documentation:
https://toolset.com/documentation/user-guides/digging-into-view-outputs/
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 |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 6 replies, has 2 voices.
Last updated by 6 years, 7 months ago.
Assisted by: Christian Cox.
Hi,
I think I found a bug in the Loop Wizard, to much code in Bootstrap grid and Table-based grid. See images
Cheers
Peter
[wpv-layout-start] [wpv-items-found] <!-- wpv-loop-start --> <wpv-loop wrap="1" pad="true"> [wpv-item index=1] <div class="row "> <div class="col-sm-12">[wpv-post-body view_template="Loop item in Blogs - voor persoonlijke teampag. (views)"]</div> </div> [wpv-item index=other] <div class="col-sm-12">[wpv-post-body view_template="Loop item in Blogs - voor persoonlijke teampag. (views)"]</div> [wpv-item index=pad] <div class="col-sm-12"></div> [wpv-item index=pad-last] <div class="col-sm-12"></div> </div> <======================================================== </wpv-loop> <!-- wpv-loop-end --> [/wpv-items-found] [wpv-no-items-found] <strong>[wpml-string context="wpv-views"]No items found[/wpml-string]</strong> [/wpv-no-items-found] [wpv-layout-end]
[wpv-layout-start] [wpv-items-found] <!-- wpv-loop-start --> <table width="100%" class="wpv-loop js-wpv-loop"> <wpv-loop wrap="2" pad="true"> [wpv-item index=1] <tr> <td> [wpv-post-body view_template="Loop item in Blogs - voor persoonlijke teampag. (views)"] </td> [wpv-item index=other] <td> [wpv-post-body view_template="Loop item in Blogs - voor persoonlijke teampag. (views)"] </td> [wpv-item index=2] <td> [wpv-post-body view_template="Loop item in Blogs - voor persoonlijke teampag. (views)"] </td> </tr> [wpv-item index=pad] <td></td> [wpv-item index=pad-last] <td></td> </tr> <============================================================== </wpv-loop> </table> <!-- wpv-loop-end --> [/wpv-items-found] [wpv-no-items-found] <strong>[wpml-string context="wpv-views"]No items found[/wpml-string]</strong> [/wpv-no-items-found] [wpv-layout-end]
I don't see anything that will produce invalid markup here. Take a look at this screenshot. In the first loop example, your loop is set up with wrap="1". That means there will only ever be one item per row, so index=other, index=pad, and index=pad-last are irrelevant and will never be used. Nothing to worry about here unless you modify the "wrap" settings, in which case you should recreate the loop using the Loop Wizard again.
In the second loop example, the code is accurate. Wrap is set to "2" with pad=true, meaning there will always be two results per row. In the case of an even number of results in the View, the wpv-item index=1 and wpv-item index=2 blocks will be rendered. That includes an opening tr and a closing tr. In the case of an odd number of results, index=1 and index=pad-last will be rendered. That includes an opening tr and a closing tr. So in either case, the number of opening and closing tr tags is correct.
