Issue with standard Global Variables inside Low Variables
Hi Low,
I have LV 2.3.0 and seem to be having issues with some standard global variables:
{segment_1} on up.
{current_time format="%Y %m %d %H:%i:%s"}
{encode}
{location}
{template_edit_date format="%Y %m %d %H:%i:%s"}
These are in a LV with early parsed turned on though, without that turned on it's not doing anything different as far as I can tell.
I'm not having issues with segment outside of the LVs
I've tested on my local machine, remotely on two different servers and on 2.5.1 and 2.5.2
I've disabled every extension and most of the modules.
Hoping for some direction
Replies
Natetronn 7 Jun 2012 23:50
Note: I'm just getting the variables themselves ie. {segment_1} instead of the actual url segment.
Natetronn 7 Jun 2012 23:53
{preload_replace:variable_name="replacement"} doesn't seem to be working either
Natetronn 8 Jun 2012 00:55
Okay, apparently this:
{exp:low_variables:single var="my_var"}
and this:
{my_var}
aren't the same things!
Low 8 Jun 2012 07:14
Indeed they're not. Check this blog post: http://gotolow.com/blog/parse-order-a... to see of that explains things.
Natetronn 8 Jun 2012 15:41
Somehow I missed the part in the docs which said single tags could not be parsed early and were *only* parsed at stage 5. The blog post does indeed explain this very well, however.
Maybe a note right up top explaining that the tags will be parsed a stage 5 and that they don't allow for early parsing (stage 1) would be nice.
Something like this:
Thanks!