Early parse variables not available in field drop down?
I just want to make sure I'm doing this properly. There may be a better way of handling this...
I have a variable (lv_widgets_blog_entries) which is an embed that queries for 6 blog entries from the other site in my MSM setup:
{embed="blog:_widgets/_listing_ul" site="blog" channel="blog" dynamic="no" limit="6" status="published|open" sort="desc" orderby="blog_entries_publish_date"}
If I put it into my template like this:
<div class="inner p15">
{home_widget_1_description}
{lv_widgets_blog_entries}
</div>
Everything is fine - but it needs to be set as an early parse in order to function. The problem is that I want my user to be able to choose this variable through the publishing interface. Basically, the user inputs a description, chooses the variable widget, and voila. But I cannot make this happen because the early parse variables are not available in the field drop down.
If I don't make this an early parse variable, and try this:
<div class="inner p15">
{home_widget_1_description}
{home_widget_1_variable} {!-- this is the name of the variable drop down --}
</div>
I only get the name of the variable on the page:
{lv_widgets_blog_entries}
Thoughts, ideas? Am I doing this all wrong?
Replies
Low 14 Aug 2012 10:35
The reason why the fieldtype only shows late parsed vars, is because the field itself will parse *after* early parsed vars, which will just create even more confusion.
You can try setting the lv_widgets_blog_entries as a late parsed var, but then use the tag syntax in your template, eg: {exp:low_variables:single var="{home_widget_1_variable}"} (which is the name of the LV field, right?)
Vaughn D. Taylor 14 Aug 2012 18:40
Yes! That worked! Thank you so much!