|
NN6 Fix Frequently Asked Questions
1. Once the fix has been applied, will my pages still work in older browsers?
2. Will the fix work in GoLive 4? CyberStudio 3?
The NN6 Extend Script can only be installed on AGL5, because older versions lack the 'Extensibility via JavaScript' functionality (via 'Extend Script' module), however,
AGL4:
If you replace AGL4's 'JScript' folder with the new NN6-compatible 'JScripts' folder, AGL4 will write the updated (NN6-compatible) action code as well. You can update a site's script library in AGL4 by deleting it, and then saving a page that is using actions and is set to 'Import Golive Script Library' (this will create a new script lib with the updated javascript code).
Writing the '<csaction>'s end tag doesn't work in AGL4, because changing the corresponding 'end tag' option in the 'Web Database' has no effect (that was a bug in AGL4), but since NN6 only shows problems if the number of '<csaction>' tags exceeds a certain amount (we've discovered that to be '72'...), this might be no problem with most pages. Adding the '</csaction>' end tag by hand in source mode doesn't help, because AGL4 rewrites the source code every time the document view is switched.
A possible workaround for the missing </csaction> end tag would be stripping all GoLive-specific tags from the HTML code on site export (under 'Site/Export Site' - click 'More...' and then check the corresponding 'Cyberstudio Tags' checkbox).
-----------------------------------------
Cyberstudio 3:
Replacing Cyberstudio 3's 'JScripts' folder with the new one will result in a 'Cyberstudio has detected one or more corrupted JavaScript action files...' warning when launching the application - that's because some actions contain action parameter types, such as 'GLActionFunctionParam', that are not compatible with Cyberstudio 3 (those parameter types were introduced with AGL4).
3. Will there be localized versions of the fix?
Yes, we are working on it now. A schedule for localizations is being set.
4. Can I use the English version of the fix on my localized copy of GoLive 5?
The English version should run on localized French and German copies of GoLive 5.
5. Should I delete the SDK 5.0r4 folder after running the fix?
No, you need to keep the SDK 5.0r4 folder for the extend module to work. Since the NN6 fix runs off the extend module, it is required that it be installed.
6. After installing SDK 5.0r4 can I safely delete any older version of the SDK?
7. My Windows GoLive version shows a creation date of Sept 17, 2000, not 08/07/00 or 08/17/00. What should I do?
Chances are you have a Try & Buy of the software. In this case, please call customer support and they will send you a new GoLive application CD free of charge. Using the version on the new CD will enable you to install the NN6 Fix.
8. I’ve run the fix and now I have dozens of orange HTML tag icons with question marks in them in the head section of my document. Did I do something wrong? Does it matter that they are there?
After updating, you need to set the ‘<csaction>’ end tag option (under ‘Websettings’) to ‘Required’. This will make the misaligned end tags (question mark icons) disappear, because now they are associated with their corresponding start tags.
9. Should I modify both the <csAction> (singular) and the <csActions> (plural) element’s end tags?
You only need to set the end tags for the <csAction> (singular) element.
|
