<xf:callback>:
public static function getValue() {
return $_COOKIE['cookieKey'];
}<xf:set var="$myValue">
<xf:callback class="XF\MY\Class" method="getValue"></xf:callback>
</xf:set>
<xf:foreach loop="$xf.app.db.fetchAll('SELECT item FROM xf_table')" value="$data">
<xf:if is="({$data.item} == '1' AND {{$myValue}} == 'abc')">
<h1>Hello World</h1>
</xf:if>
</xf:foreach>// initial response -- write cookie
\XF::app()->response()->setCookie('cookieKey', 'cookieValue');
// later request -- read cookie
$cookie = \XF::app()->request()->getCookie('cookieKey');
The application pane will show a live view of currently set cookies, but the actual cookies sent with any given request can vary. If you look at the request headers in the network pane, you can see the cookies which were sent to the server for the selected request:
Related to value escaping, for security. Are you trying to
<xf:set var="$foo"><xf:callback ... /></xf:set>? If you want to make variables available in a page template, it's best to do what I suggested in my first reply here.
What you mean? I didn't get it.
Right I'll try it now. Where do I find that callback field in page template? I see only title and textarea
Cookies set in one response to a request are not present in the same request. They will only be present in future requests.
They are in the page node options, if you are rendering your template with a page node.
Actually, as I said, it's a feature in PAGE_CONTAINER, not really a page node.
How can I deal with this callback return? How to read it? Some include method?
Right, sorry. You would typically introduce new page behaviors (and template parameters) by extending a controller. If you need to do this more globally, you can use code events (like
templater_template_pre_render or templater_global_data) to add parameters (variables) to templates.In any case, the callback should work ok. It will output its contents where the
<xf:callback> tag is placed. If you are saving the value to a variable by wrapping it in <xf:set>, you will get back a pre-escaped object but you should still be able to render it like any other variable:<xf:set var="$output"><xf:callback class="Some\AddOn\Class" method="getOutput" /></xf:set>
{$output}$xf.request.getCookieRaw('cookieKey'). Since you don't need <xf:callback>, you can store the unescaped value using the alternate <xf:set> syntax:<xf:set var="$cookieKey" value="{{ $xf.request.getCookieRaw('cookieKey') }}" />$cookieKey in conditionals like you expect. Apologies for the confusion, though I would still caution against placing this sort of logic directly in templates (even if it is technically possible). It works in a pinch but would likely fall outside of the resource standards for add-ons.
Awesome @Jeremy P , exactly what I was looking for! Very simple! How can I get full syntax XF list? Any documentation?
XenForo is rendered server-side, and JS runs in the browser after the page has already been rendered by the server. The browser can only send cookies to the server that have already been set, so any cookies set in one request will not be visible to the server until later requests.
I mean xf methods, like $xf.request or $xf.xxxxxx
$xf variable contains global template data. You can dump it to inspect it further with {{ dump($xf) }}, or dump all variables for a given template with {{ dump(vars()) }}. The $xf.request key will give you the \XF\Http\Request object pertaining to the current request.
Great! Thank you so much!
