I have a tricky nesting scenario that I am assuming involves parse order.
I have a tricky scenario that I am assuming involves parse order. I am using Low Variables in conjunction with Transcribe. So I have a single template that will be used for multiple languages. In Transcribe you have 2 tags that will return the currently active language's abbreviation (en, es, fr, etc.) {exp:transcribe:language_abbreviation} and {transcribe:language_abbreviation}. I have setup corresponding Low Variable groups with identical variables that are appended with the language variables (_en, _es, _fr, etc.). So the idea is that in my single EE template I would call something like this:
{lv_navigation_{transcribe:language_abbreviation}}
That actually works great! Transcribe adds in the currently selected language abbreviation appended to the end and the appropriate Low Variable for that language comes up.
The issue I am running into is if I have a Low Variable with the Transcribe abbreviation tag, and then inside the LV is another Low Variable with the Transcribe abbreviation tag.
So it might be something like:
in the EE template:
{lv_header_{transcribe:language_abbreviation}}
in that LV:
{lv_navigation_{transcribe:language_abbreviation}}
{lv_tagline_{transcribe:language_abbreviation}}
So I have tried all types permeations of LV tags types and early parse settings, but I can't seem to get the second set of LV to resolve with the Transcribe abbreviation tag. The one in the template will resolve correctly though.
Any help?
Replies
Low 18 Dec 2013 08:33
Yeah, that's parse order for ya.
If you're using Textarea variable types, you might be able to work around it using its preparse parameter.