Understanding Stash Variables

Question

I'm using Stash 2.3.6 beta. Can somebody explain why this works:

{exp:stash:set name="var1"}no{/exp:stash:set}
{exp:stash:set name="var1"}yes{/exp:stash:set}
{exp:stash:get name="var1"}

Where I get "yes" as output.

But this does not:

{exp:stash:set name="var1"}no{/exp:stash:set}
{exp:channel:entries channel="promos" limit="1"}
    {exp:stash:set name="var1" replace="yes"}yes{/exp:stash:set}
{/exp:channel:entries}
{exp:stash:get name="var1"}

Where I get "no" as output, but expect "yes".

I'm guessing it has to do with the parse order, and that channel:entries happens after everything outside of it is parsed. I looked at the parse order docs (The Template Engine), and it looks like channel:entries are processed on step 15, module and plugin tags. Not sure where Stash gets processed.

But, speaking of which, I did try adding process="end" to the get. That got me a funky looking output: {357b280a38bad6479603b312799efcb0422985159}

Any help appreciated.

Answer 1

Such seemingly random strings can be a symptom of the Stash extension not being activated. Worth a check.

Those strings are used by Stash as placeholders getting replaced by the stash extension. If the stash extension is not activated, they never get replaced.

Answer 2

Yes, this is a parse order thing, the get is parsed before the second set, since it is within a channel entries tag pair. But this should work:

{exp:stash:set name="var1"}no{/exp:stash:set}

{exp:channel:entries limit="1"}
  {exp:stash:set name="var1" replace="yes"}yes{/exp:stash:set}
{/exp:channel:entries}

{exp:stash:parse process="end"}
  {exp:stash:get name="var1"}
{/exp:stash:parse}

But in general, you won't get very far with setting and getting data within the same template. That's why the template partials approach sets data in the base template and then gets it in an embedded template.