|
|
Browse by Tags
All Tags » merges
-
The majority of the merge codes that you have added to you content page will not function on content pages as they were not designed to. These merge codes were designed to aid in the customization of product and category page layouts. They will function if placed inside a custom HTML snap-in added to a category or product in the catalog ...
-
I am trying to add the category short description to the category page, so I added a custom HTML snap-in onto the category page and added the following merge code: ##CATSHORTDESC##
But for some reason, it's not translating it to the short description, it is just showing the merge code. You can see it in action ...
-
I'm trying to use a conditional site merge based on the store ID - but it doesn't seem to be working. I'm using it in both if / endif and if / else / endif ways, as shown below... But I might not have the right store IDs. I got my store IDs by showing the total request time line at the bottom of each page.
Of course, ...
-
I'm trying to use the ##ATTRIBUTEDETAILS## merge - it's not working, and I can't figure out why. I've simply entered the merge:##ATTRIBUTEDETAILS##into a Custom HTML snap-in in various areas: the home page center content, the left column, the category pages, the catalog pages... and all that results is the characters ...
-
Hello,
The attribute snap-in is only used when you DO want the drop-down menu.
For the attribute 'browse' option, you need to use the merge (you can add it to a Custom HTML snap-in):
##ATTRIBUTEDETAILS## - a formatted output of all attribute groups, their values and their attribute names ...
|
|
|