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: Africa/Casablanca (GMT+01:00)
This topic contains 4 replies, has 3 voices.
Last updated by 3 years, 3 months ago.
Assisted by: Jamal.
8) Content Templates...I think this is where I'm most confused (e.g. what's the difference between Used on "SEACommnications (single)" vs. "This Content Template is used as the loop block for the View..." I suspect this, or the query filter, is where I've gone wrong.
Okay the difference you're describing is one of assignment. Content Templates can be used in many different ways. One use of a Content Template is where you apply one Content Template (CT) to be used on all posts in a post type. That's what "Used on SEACommunications (single)" means, in general. When any SEACommunications post is loaded on the front-end of the site, this CT will be applied to the post and displayed in the main post content area. Dynamic sources in the template can be configured to display information from the current post, so if you have a Single Field block with a custom field coming from a dynamic source in the current post, the value of the current post's custom field will be displayed there on the front-end.
"This Content Template is used as the loop block for the View..." indicates a different type of assignment for a Content Template. This template is used to design the contents of the loop of a specific View. See the screenshots ct.png and wizard.png attached here. When you use the Loop Wizard during development of a View, by default, a Content Template will be created to hold the contents of one iteration of the loop. Everything you place in the loop template will be repeated for each result in the View. In the code area, you can see the loop template is placed inside the wpv-loop tags using a wpv-post-body shortcode. This is most helpful for complex loop types or loops that contain a large amount of information, and also is required if you want to design the contents of the loop using the Block Editor.
If you disable the CT option in the Loop Wizard, the contents of the loop will be placed directly in the loop output panel where you now see the wpv-post-body shortcode, and no loop template editor would be shown below the loop editor area.
Now that we've discussed loop templates and how they work, let's look at the one you have set up here:
hidden link
This is the loop template for the View of outer RFGs - Article (parent)s. I can see that you have placed a couple of shortcodes here that you want to use to display the inner RFG fields. The problem here is that you need a View to display the contents of the inner RFGs here. It's the same reason you use a View to loop over the outer RFG in the template for SEACommunications. There can be multiple Article (parents) associated with each SEACommunication post. In the same way, there can be multiple Article (child) associated with each Article (parent). So you can't just drop a single shortcode here, you must create a View of the Article (child) RFGs and place that View here in the loop template. Then put your shortcodes in the loop of THAT View to display the fields of each Article (child).
I did a quick scan of the Views you've created already and it looks like the Ralph Children View is the closest to what you'll need here, so I placed it in the loop template where you currently have the article-title-child and article-body-child shortcodes. You can probably delete those. Now I can see the nested RFGs appear in the SEACommunication post on the front-end of the site. Not all the Article (parents) have Article (children), so obviously there aren't children displayed for all parents. In those cases you currently see "No items found" because that's how the Ralph Children View is set up to display when there are no items found:
hidden link
You may want to adjust that. I'm a little confused by what I'm seeing now, so I think it's time for you to jump in and take another look. Considering the nested RFG content, I see there are two wpv-post-body shortcodes in the loop of the Ralph Children View, so I would start my investigation there to understand what is going on. You may need to revise the contents of those templates, or delete one or the other of them, because I see the SEACommunications and Table of contents headers repeating over and over and that looks odd.
Let me know what you need next.
