Hot answers tagged

4

The nested instances of switchee should not have the exp prefix. {exp:switchee variable="{variable_1}" parse="inward"} {case value="{variable_1}"} {switchee variable="{variable_2}" parse="inward"} {case value="{variable_2}"} some text {/case} {case default="yes"} some other text {/case} {/switchee} {/case} ...


2

A plugin like Child Categories may help you with this: http://devot-ee.com/add-ons/child-categories


2

you issue is that all your records have class="active". It is happens because count is going from exp:channel:entries and for all playa records is the same - 1. You have already var_prefix parametr for playa:children, so you just need to add it into condition. <ul class="pill tabs-content contained"> {exp:playa:children field="...


1

Use the parse="inward" parameter. {exp:gwcode_categories cat_id="{category_id}" incl_self="no" style="linear" parse="inward"} Which will ensure {cat_id} is set prior to the channel:entries tag being run.


1

Here was the final solution. {exp:playa:children field="3rd_order_under" sort="asc" var_prefix="thirdorder"} <li {if '{thirdorder:count}' == '1'}class="active"{/if} id="pillTab{thirdorder:url_title}Tab"> <div class="row"> <div class="twelve columns"> {thirdorder:...


1

The inner exp:playa:children tag should not be prefixed. The var_prefix is for the variables inside the tag, not for other tags. You'll want to do something like this: {exp:playa:children field="3rd_order_under" sort="asc" var_prefix="thirdorder" } 3rd count: {thirdorder:count} of {thirdorder:total_results}<br> 3rd url_title: {...


1

To try and get a handle on what's going on, I would break things down to just the variable output and forget about the html markup until it makes sense. Try this and see if you can pinpoint it: {exp:playa:children field="3rd_order_under" sort="asc" var_prefix="thirdorder" } 3rd count: {thirdorder:count} of {thirdorder:total_results}<br&...


1

You have still included your JavaScript in the wrong order, jQuery should come first. How it is now: <!-- More Foundation pannel --> <script src="http://niwot.colorado.edu/eejavascripts/jquery.foundation.tabs.js"></script <!-- END More Foundation pannel --> <script src="http://niwot.colorado.edu/eejavascripts/jquery.js"></...


1

It's certainly going to be more resource heavy that way, to be sure. One thing that could definitely help would be to use the early parsing conditional add-ons, switchee and ifelse to evaluate the conditionals. Your outer condition is a good spot for switch case logic, while your interior could use ifelse: {exp:switchee variable="{member_group}" parse="...


1

Relationship tags are nest-able by continuing with the colon syntax: {parents:parents field="case_study_related_client"} <p><a href="{parents:parents:title_permalink="case-studies/index"}">See how we helped {parents:title}</a></p> {/parents:parents}


1

From comments above from Mark Croxton: Channel Entries can't be nested but exp:stash:set_list and exp:stash:get_list have no problem, providing you append a 4th tagpart to the nested tagpair and use the prefix parameter. As far as I can tell you need a very similar solution to this one: Nesting channel entries in Stash - but you need to output the same ...


Only top voted, non community-wiki answers of a minimum length are eligible