New product image template

[NormanRouxel]

It would be much cleaner to do this

<!-- ProductImage HTML begin -->
<!-- This file is used to build the product image markup. -->

<IMG SRC="NETQUOTEVAR:IMAGEFILE"
ALT="NETQUOTEVAR:ALTERNATETEXT"
ALIGN="CENTER"
BORDER=CUSTOMVAR:BORDER
NETQUOTEVAR:IMAGEHEIGHT
NETQUOTEVAR:IMAGEWIDTH
NETQUOTEVAR:OTHERIMAGEMARKUP>

<!-- This file is used to build the product image markup. -->
<!-- ProductImage HTML end -->

and set the Customvar BORDER to 0 globally and to whatever you want per product.

Alternatively replace BORDER=CUSTOMVAR:BORDER with simply CUSTOMVAR:BORDER and set it to "border=0" globally and "border=1" per product. This would let you add in differnt things like "style=....." instead.

[jont]

Hi Norman - its not the border causing the issue it is the ALT text not being implemented when calling the modified product image template from the product line

[NormanRouxel]

Got you. This may be an Actinic buglet. The help file says

'Is File Name' and 'Use File Content'.

Note: This file can contain any NETQUOTEVARs and CUSTOMVARs that have valid values available.

So perhaps this should be interpreted as - NETQUOTEVAR:PRODUCTIMAGE is valid within a product template but the netquotevars that are only valid within NETQUOTEVAR:PRODUCTIMAGE aren't necessarily available.

I do know that you can access NETQUOTEVAR:IMAGEHEIGHT within the Product Template so it does seem as though Actinic isn't being consistent in applying these rules.

[domino1]

Norman,
Which version are you using? Bill (wjcampbe) doesn't appear to see the problem with Catalog V7 (see post #23 in this thread). I'm currently using V6.14.

BTW, agreed setting the border using a customvar would be a lot neater but I'm actually trying to do something a little more complex that requires a different ProductImage template. The border setting was just so I could see a difference to begin with.

As a work around I'm now setting my own ALT text using a customvar. A little annoying but it works.

[NormanRouxel]

I was looking via 7.0.4. I didn't investigate which ProductImage variables would be parsed via 'Use File Content' in V6 at all. It's unlikely that any such minor bugs will ever be fixed in V6.