X-Cart forums

[totaltec]

Well the language variables are pulled from the DB, and placed in the template, smarty variables contained inside them are not processed normally.

But using |substitute makes it look for that {{tag}} that you specify, and then it can evaluate the variable and include it in the string. Glad you got it sorted.

[hooter]

Alternatively and possibly simpler solution would be:
Language variable would contain this exactly as Steve suggested:

<a href="home.php"><img src="{$AltImagesDir}/custom/mypicture.jpg" /></a>

Then call the language variable in your tpl file thusly:

{eval var=$lng.languagevariablename}

Essentially you can treat a variable as a template and embed entire smarty constructs within then using eval function outputs the variable contents.

Originally Posted by tartaglia

So here's the result...

Sorry Steve your suggestion...

<a href="home.php"><img src="{$AltImagesDir}/custom/mypicture.jpg" /></a>

doesn't work, but thanks.

What does work is...

<a href="home.php"><img src="{{AltImagesDir}}/custom/mypicture.jpg" /></a>

if you call it like this from the tpl file...

{$lng.languagevariablename|substitute:"AltImagesDir":$AltImagesDir}

I believe this is because the language variable itself can't pass through the real value of the smarty variable. Therefore they use the {{ }} to identify a value that can be called out by the substitute function and in the substitute function they replace the AltImagesDir with the smarty variable {$AltImagesDir} which of course the tpl file know.

There ya go, it works now. All that to avoid hardcoding the path in the language variable, not sure it was worth it but a good learning exercise. Feel free to give a more proper explanation of why it works if you want. I am not a developer.

[totaltec]

Originally Posted by hooter

Alternatively and possibly simpler solution would be...

Very nice! I had forgotten about eval, you can use that to enable variables in product descriptions as well I believe. Thanks hooter!

[tartaglia]

Awesome hooter, I will try that as well. Does it hurt anything to have the {eval var=$lng.languagevariablename} if there is no {$something} in the langauge variable? I'm gussing not.

What a world of possibilities opens up!

[totaltec]

Originally Posted by tartaglia

Does it hurt anything to have the {eval var=$lng.languagevariablename} if there is no {$something} in the langauge variable? I'm gussing not.

There is probably a small performance impact. Since it has to check if the string contains something to evaluate.