Overall Layout Templates

[Ben Turner]

Hi

I've edited the 'overall layout' tab of some of the sections in my catalog with my own template to allow me to promote other sections on the right hand side of the page. See this page for an example. It seems to work and i can have different products promoted on any page i want. However, when new files are uploaded the live site gives an error message 'expected hexadecimal digit' - whatever that means! It doesn't appear to be affecting functionality of the site but doesn't look good. Does anyone have any ideas?

Thanks

Ben Turner

[ditch]

Please attach the primary templates you've altered so we can take a look

[Ben Turner]

file attached

[NormanRouxel]

Had a quick look. It's a JavaScript error message you're getting. I see that you have all the Actinic Section structures included (in Act_Primary.html) although I didn't see you using them. Also I found some images using the Ampersand character in the file name. I'd recommend using cleaner image names.

E.g.

<a href="FRS_Countrywear_Lyle_and_Scott_81.html"><img src="l&s_th.jpg" width="60" height="9" border="0" alt="Lyle &amp; Scott"></a><br>

Now if you have similar things in your section names this may be causing bad code in your section structures.

Norman

[cdicken]

I'm also wondering if there is some unacceptable code within the custom js file

<script type="text/javascript" language="JavaScript" src="/javascript/macfix.js"></script>

...that you refer to in the template. Try removing this line and uploading.

[Ben Turner]

i don't think there is a problem with macfix.js. it seems to work fine on my pages outside of the catalog. it just resolves a display problem we were having with mac users. I noticed Actinic automatically uploaded a lot of js files when i used a new 'overall layout' for a section. What are they for?

[NormanRouxel]

I think you've accidentally included the large list of Sectiontree Javascript files. I don't see you attempting to use these on your pages.

These are usually commented out in Act_Primary.html. If you look in Actinic Ecommerce V6 / Formats / Themes and look for the appropriate Act_Primary then you can see it in its orginal state.

Norman

I aslo checked your macfix.js file and it doesn't seem to be responsible for the error you get.

[Ben Turner]

Thanks Norman

I can see in the source of the live pages that there are a lot of scripts eg.

<SCRIPT LANGUAGE="JavaScript" SRC="Act_section_tree.js" TYPE="text/javascript"></SCRIPT>

I can't see that there is anything in act_primary (or my edited versions of act_primary i'm using as layout templates) that refer to these scripts. Which template should i be editing to remove the sectiontree js files?

Thanks

Ben

[NormanRouxel]

Act_Primary.html. Look for lines like

<!--
The NETQUOTEVARs below can be uncommented for getting raw section lists:
1. Top level section list
2. Section list from current level and all children
3. The whole section tree
The rest covers the standalone structure members for each array - e.g. if
you only need sName or sURL from an array.
See the documentation for details.

NETQUOTEVAR:TOPLEVELSECTIONS_RAW
NETQUOTEVAR:CHILDSECTIONS_RAW
NETQUOTEVAR:SECTIONTREE_RAW

NETQUOTEVAR:SECTIONTREE_NAMES
NETQUOTEVAR:SECTIONTREE_URLS
NETQUOTEVAR:SECTIONTREE_IMAGES
NETQUOTEVAR:SECTIONTREE_IMAGEWIDTHS
NETQUOTEVAR:SECTIONTREE_IMAGEHEIGHTS
NETQUOTEVAR:SECTIONTREE_SECTIONIDS

NETQUOTEVAR:TOPLEVELSECTIONS_NAMES
NETQUOTEVAR:TOPLEVELSECTIONS_URLS
NETQUOTEVAR:TOPLEVELSECTIONS_IMAGES
NETQUOTEVAR:TOPLEVELSECTIONS_IMAGEWIDTHS
NETQUOTEVAR:TOPLEVELSECTIONS_IMAGEHEIGHTS
NETQUOTEVAR:TOPLEVELSECTIONS_SECTIONIDS

NETQUOTEVAR:CHILDSECTIONS_NAMES
NETQUOTEVAR:CHILDSECTIONS_URLS
NETQUOTEVAR:CHILDSECTIONS_IMAGES
NETQUOTEVAR:CHILDSECTIONS_IMAGEWIDTHS
NETQUOTEVAR:CHILDSECTIONS_IMAGEHEIGHTS
NETQUOTEVAR:CHILDSECTIONS_SECTIONIDS

The section level can be accessed through:
NETQUOTEVAR:SECTIONLEVEL
-->

Note how these are all commented out. That will get rid of them.

Norman.

[Ben Turner]

Norman

Thanks for the reply. The code that you mention is already commented out, which is why i couldn't understand why all the scripts were in the source of the live page. However, i've just cut all the commented html you mention out of the template and updated the site. It appears to have fixed the problem. It seems that simply commenting it out doesn't have the desired effect

Thanks for all your help

ben