Act_setion_tree.js Bug

[Martin Smith]

I have uncommented the NQV SECTIONTREE_RAW in my Act_Primary.html template in order to use the file Act_section_tree.js to build a dropdown box.

However because of the poor structure of this file it is causing errors within many browsers (notably IE 6SP1).

Upon further inspection I found that each element of the array contains an attribute called sImage, this holds the path to the section image. Because this is a file path, it contains forward slashes, some of which correspond to JavaScript escape sequences and cause errors. For example the line

section_tree[6].pChild[1].sImage = "images\xraymachine.gif";

would cause the browser to error because \x is the escape code for hex, so the browser expects a hex code after it.

Hopefully I have made the problem clear. Therefore I would like to know:

1 Is this a known issue and if so why it isn't mentioned in the kb?
2 Are there any plans to fix Actinic so that it writes a proper string using appropriate escape characters (\\ not \)?

[cdicken]

This problem was fixed in v6.1.0 of Actinic. You must be on an earlier one (check in 'Help | About...')

You can get hold of the latest version of the software from http://www.actinicdownloads.com/v6

[Martin Smith]

Thanks for your reply Chris, however it seems that what you say is incorrect. Please find attached an image showing my Actinic About Page.

My original version (as installed from the CD) was "6.1.1.0.0.0 DDOA", I have run one patch, filename: "Actinic CatPatch613.EXE" downloaded on 10/07/2003 in order to be on my current revision number.

[cdicken]

Hmmm, you are correct.

It looks like 'Act_sections.js' was fixed (for the top-level section list only) but there is still an outstanding problem with 'Act_section_tree.js'.

Apologies - I was rather let down by my information.

I'm afraid the only workaround for the time being is to move your section images into your 'Site1' (or equivalent) folder in order to remove the '\' characters from the Act_section_tree.js file.

[Martin Smith]

Thanks for your replies Chris, FYI, I have tried un-remming NETQUOTEVAR:TOPLEVELSECTIONS_RAW in order to create Act_Sections.js and this file doesn't appear to have been fixed at all!

For example it contains the following line:

sections[6].sImage = "images\manufs\xerox.gif";

For the meantime I will use the workaround you suggest and loose some SEO strength (better than telling a customer not to use any images starting with an O or a X!).

Are there any plans for a bugfix for this? Surely it shouldn't be hard or time to consuming to patch Actinic so that it parses the string for "\" and replace with "\\" before writing it to the .js file!

[cdicken]

Hmm... thanks for that. I'll get back to the development team.