I'm using the MVVC approach and all works well until I turn on fragment caching. This works, but of course does not offer any performance advantages.
`{exp:stash:set_list
name="tutorials"
parse_tags="yes"
parse_conditionals="yes"
parse_depth="2"
}
{exp:channel:entries
channel="tutorials"
dynamic="no"
disable="member_data"
}
{stash:item-entry-id}{entry_id}{/stash:item-entry-id}
{stash:entry-title}{title}{/stash:entry-title}
{exp:stash:set_list:nested
name="tags"
context="{entry_id}"
parse_tags="yes"
}
{exp:tagger:tags entry_id="{entry_id}"}
{stash:tag-url-name}{tagger:urlsafe_tagname}{/stash:tag-url-name}
{stash:tag-name}{tagger:tag_name}{/stash:tag-name}
{/exp:tagger:tags}
{/exp:channel:entries}
{/exp:stash:set_list}`
If I set it to save using the following parameters, the tags are not shown anymore:
{exp:stash:set_list
name="tutorials"
parse_tags="yes"
parse_conditionals="yes"
parse_depth="2"
save="yes"
scope="site"
refresh="5"
replace="no"
}
My layout template where I get the tags looks like this (other markup and stash data removed for clarity):
{exp:stash:get_list name="tutorials" paginate="bottom" limit="10"}
<p class="custom meta">
<span class="fa fa-tags">
{exp:stash:get_list:nested
name="tags"
context="{item-entry-id}"
prefix="nested"
backspace="2"}
<a href="/search/tag/{nested:tag-url-name}" rel="tag">{nested:tag-name}</a>,
{/exp:stash:get_list:nested}
{/exp:stash:get_list}
I suspect it is caching the first set_list data before it actually parses the nested list that gets the tag data. I did try to use:
{stash:embed:layouts:listing-text parse_stage="both"}
But that didn't work.
Maybe this approach (using a set_list) isn't the best way to do this. The page is a listing of entries and I want to be able to use pagination and switchee cases to allow for displaying filtered content by category and tag using regex with switchee.