Custom Naviation Buttons

[Charlesn]

I'm in the process of re-arranging my site, and am breaking it down into differently branded sections. As my buttons created for my original Act_Primary no longer fit in with the new branding, I've created loads more buttons to use within my 3 new Act_Primary sections. I've used a piece of HTML from the advanced userguide which lets you insert individual buttons, and then define which NETQUOTEVAR they need to be assigned to (Up, Back, View Cart Etc..). But I don't need to use all the buttons all of the time (Like 'Back' for instance) so do I need to make more Act_Primary sections for as you move further through the shop? Or will Actinic only use the necessary buttons as and when they are needed?

Since I'm pretty useless when it comes to hard coding and generally dealing with HTML, I don't want to slam all the new coding into place only to find its not really needed, or I need to add or subtract loads of it!

Anyone got any ideas?

Thanks
Charles

www.ahapremier.com

[cdicken]

I know you have spoken to Menar about this, but here is an answer for the records.

If you use your own images and then use the navigation link variables for the hyperlinks e.g.
<a href="NETQUOTEVAR:NAVBCARTLINK">...</a>
<a href="NETQUOTEVAR:NAVBBACKLINK">...</a>
etc.
then the links on some of the buttons will be context sensitive.

The ones that cause trouble are
NAVBSITEMAPLINK (only on front page)
NAVBCATALOGLINK (all except front page)
NAVBBACKLINK (all except front page)
NAVBUPLINK (all except front page)

The way around this is to not bother using 'BACK' or 'UP' and just use hard-coded values for the 'CATALOG' and 'SITEMAP'.