It’s getting late, my eyes are sore, and I don’t know why this template code:
{exp:weblog:entries weblog="galleries_2007" limit="1"}
{entry_id}
{exp:esk_faf:nominated_artists gallery_id="{entry_id}" year="2007"}
{yby_trans}
{yby_year}
{yby_media}
{/exp:esk_faf:nominated_artists}
{/exp:weblog:entries}
is getting its entry_id (and other weblog_titles data) parsed but not the custom fields. They are just being removed. I have looked in all of the arrays of data in the plugin and all SQL results are correct, it’s a parsing issue. The parsing is simple though, prep_conditionals, then swap the vars.
When I look in $TMPL->var_single it is an empty array (or an array containing only {entry_id}.
Any ideas, I’m starting to consider a career change.
Glen.
esk_faf is a plugin. I have stripped the template code down for clarity but imagine I have:
{exp:weblog:entries weblog="galleries_2007" limit="1"}
{entry_id}
{exp:esk_faf:nominated_artists gallery_id="{entry_id}" year="2007"}
<div>
{yby_trans}
{yby_year}
{yby_media}
</div>
{/exp:esk_faf:nominated_artists}
{/exp:weblog:entries}
it would return:
21369
<div>
</div>
<div>
</div>
Which is correct, except all the variables have gone, I have check the SQL results through the process of the plugin and they contain all of the correct data - it even returns 2 set of empty html so it knows how many records are returned.
I think it is perhaps an issue with the multiple site manager and the cache - so I’m looking into that now.
All the same, was the plugin properly returning the $TMPL->tag_data string?. Could be many issues at play here. For example if the {yby_etc} variables belonged to the parent (wrapping) weblog then they would be parsed out before the plugin got to see its tagdata - so echo’ing or print_r’ing $TMPL->var_single, from within the plugin code, would result in nothing being shown.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.