Using Stash inside of other variables

Question

I am storing site settings using stash and would like to pull out the email address from stash and use it in the EE encode tag. Does anyone know if this is possible?

I have tried a few different things. Lastly this...

{encode="{exp:stash:get name='email'}?subject=Information About a Home" title="Email Us"}

It isn't rendering the stash variable inside the encode tag. Instead, I get the following:

<span data-eeencemail_tzeaewnqdt="1">
    <a href="mailto:?subject=Information About a Home">Email Us</a>
</span>

* EDIT *

How I set the stash:

{!-- CONTACT EMAIL --}
    {exp:stash:email}{contact_email}{/exp:stash:email}

* SOLUTION *

I was able to use this by utilizing the parse tags in stash to get around the parsing order on output.

So instead of this:

{encode="{exp:stash:get name='email'}?subject=Information About a Home" title="Email Us"}

I did this:

{exp:stash:parse}
    {encode="{exp:stash:get name='email'}?subject=Information About a Home" title="Email Us"}
{/exp:stash:parse}

which worked perfectly.

* BETTER SOLUTION *

Even thought the above worked (Which I'm leaving in case someone didn't know about the stash parse tags), @natetronn's solution was much better since it uses the short syntax. Using the short syntax, it becomes this:

{encode="{exp:stash:email}?subject=Information About a Home" title="Email Us"}

Answer 1

I'm not totally sure if it matters but, I see you're setting your var using the Set shortcut syntax. Try getting using the Get shortcut syntax as well i.e. {exp:stash:email} That is, try not to mix syntaxes.

I'm curious to know if that makes a difference?

Answer 2

I'll assume your variable was SET previously in the parse order.

Were you doing this by any chance?

{!-- test: does this work? --}
{exp:stash:get name='email'}

{encode="{exp:stash:get name='email'}?subject=Information About a Home" title="Email Us"}

If so, you'll have come across a parsing 'feature' in EE whereby identical calls to the same tag causes them to be cached. What happens is that after parsing the first instance, EE replaces the subsequent instances of the tag with markers that gets replaced at the end of parsing, after other tags have been parsed. This can have the unfortunate result that markers netsed inside other tags or passed as parameters get marooned (and since this is usually what you want to do with a stash variable, it causes a problem):

{!-- test: does this work? --}
[email protected]

{encode="M0100749435475676575675?subject=Information About a Home" title="Email Us"}

See this article for a full explanation: http://blog.ericlamb.net/2011/05/expressionengine-and-the-mystery-of-m00o93h7pq09l8x1t49chy01z5j4tt91fgfr/

To stop this happening you can append the word 'random' to the later instances:

{!-- test: does this work? --}
{exp:stash:get name='email'}

{encode="{exp:stash:get name='email' random}?subject=Information About a Home" title="Email Us"}

See: http://www.emarketsouth.com/add-ons/string-plugin/template-tags/#random-parameter

Alternatively you can access the variable as a placeholder variable inside {exp:stash:parse}, and use it as many times as you like:

{exp:stash:parse}

    {!-- test: does this work? --}
    {stash:email}

    {encode="{stash:email}?subject=Information About a Home" title="Email Us"}
{/exp:stash:parse}