using custom variables in desc

[kevster]

Does anyone know how and if you can drop custom variables into the full descrition field.

I have a site that uses forms in the full description box to post data to worldpay but want to ideally use custom variables on the property tab to pass this info in rather than hard code the info into the full desc field itself?

[Duncan Rounding]

Yes you can just add the variable name in square brackets.

As an example, for a custom variable called TestV, in the product description you can put:
This classic teapot is available in two sizes.[TestV]

[kevster]

Great - thanks Duncan will give that a go.

rgds, Kevin

[kevster]

not working for me yet - just prints out WP-DESC, have tried with and without ""

!!<

blah blah

<input type=hidden name="amount" value="34.95">
<input type=hidden name="currency" value="GBP">
<input type=hidden name="desc" value=[WP-DESC]>
<! TEST MODE VALUE IS 100 LIVE IS 0 -->
<input type=hidden name="testMode" value="0">

blah blah

>!!

Any ideas? will try with !!< >!! around

[Duncan Rounding]

Try this

!!<

blah blah

<input type=hidden name="amount" value="34.95">
<input type=hidden name="currency" value="GBP">
<input type=hidden name="desc" value=>!![WP-DESC]!!<>
<! TEST MODE VALUE IS 100 LIVE IS 0 -->
<input type=hidden name="testMode" value="0">

blah blah

>!!

[kevster]

tried that but it didnt work - this did though!

go into design tab and add the variable using the actinic controls, the new variables shuold be in the list. This then adds the variable in blue text.

The copy this and delete from the design content.

in the content tree go to the product full description and paste the variable in which then shows the proper value <actinic:variable name="WP-DESC" />.

What I was doing before was just adding text - actinic wasnt picking it up properly. maybe this works in your version? Im going to be upgrading to 8.5.2 over xmas.

Thanks for your help

[Duncan Rounding]

This is what I did intially when I was testing, but later I deleted that and tried just adding [TestV] into the description and it worked ok. I tested on v802.The CV was scoped to product - maybe that makes a difference.

[kevster]

mine is scoped to prod as well - maybe its the version difference - got there anyway!