XF 2.0 XF:set scoping
- Thread starter Ian Hitt
- Start date
That will have never worked (wouldn't have worked in XF1, either).
In XF1 the solution was:
In XF2 the equivalent is:
or
In XF1 the solution was:
Code:
<xen:container var="$var">Some string value</xen:container>In XF2 the equivalent is:
Code:
<xf:page option="$var" value="$anyValueType" />
Code:
<xf:page option="$var">Some string value</xf:page>
Jake B.
Well-known member
Just to be clear, we're including a template from within PAGE_CONTAINER (rather than in the content template) that contains several conditionals that we use a lot, it's working fine in xf1 but doesn't seem to be working in xf2
As an example, in PAGE_CONTAINER just below the doctype line:
Code:
<!doctype html>
<xf:include template="conditionals" />
{{ dump($someVariable) }}and within "uix_conditionals" we'd have:
Code:
<xf:set var="$someVariable" value="1" />We use this for things like welcome block, extended footer etc just so we don't have to duplicate conditionals, and we split it into a separate template to keep the PAGE_CONTAINER template cleaner and easier to merge down the line
<xf:set> would set the variable in the current content or container template and only be accessible in the content or container template it was set in.<xf:page> would set the variable in the current content template and make it available in the container template.Indeed looks like I misunderstood the original message.
In this case, there is a difference between XF1 and XF2. The main one being that in XF1 a compiled template consisted of the "main" template and then each included template compiled inline within that main template.
In XF2 we compile each template separately.
In other words, whereas the compiled PAGE_CONTAINER template in XF1 would include the compiled "uix_conditionals" template, in XF2 it just includes a reference to it (it's just a call to the
renderTemplate() method in the templater).Although this is a net benefit overall, it does change the variable scope slightly.
I don't have a solution available off-hand though we'll give it some thought. (You might want to consider if there's some alternative approaches you can take in the mean time).
Last edited:
Does this work?
PAGE_CONTAINER
uix_conditionals
uix_macros
PAGE_CONTAINER
Code:
<xf:include template="uix_conditionals" />
<xf:set var="$uix_conditionals" value="{{ $xf.app.templater->pageParams.uix_conditionals }}" />
...
<xf:macro template="uix_macros" name="uix_extended_footer" arg-uix_conditionals="{$uix_conditionals}" />uix_conditionals
Code:
<xf:page option="uix_conditionals.foo" value="1" />
<xf:page option="uix_conditionals.bar" value="0" />uix_macros
Code:
<xf:macro name="uix_extended_footer" arg-uix_conditionals="!">
<xf:if is="$uix_conditionals.foo">whatever</xf:if>
</xf:macro>
Last edited:
Jake B.
Well-known member
We're planning on moving these into our add-on since it's required anyways so it's not that big of a deal in this instance, but I suppose it could cause issues for other use cases just nothing else I can think of off hand
Jake B.
Well-known member
I'd think that would run into the same issue, the variable isn't available at all in PAGE_CONTAINER with xf:set and I think
xf:page only works in the content template
Lukas W.
Well-known member
Took me a while to figure that out. In fact, the correct syntax is:
Code:
<xf:page option="var" value="{$anyValueType}" />$var available in the page container.
egerci
Member
Save my life
ThanksSimilar threads
