mindgraffiti

This FAQ focuses on the GL2DW Migration Extension Tool. If you are planning on manually migrating from GoLive into Dreamweaver, check out Adobe’s helpful step-by-step tutorials. Lynda.com also offers excellent training for making the switch.

GL2DW Migration Extension Tool Help

Download a modified version of the GL2DW Extension, from Rob Keniger. The patch is  more forgiving than Adobe’s original release and no longer modifies MenuMachine code. Details about the patch in Adobe’s Forums. Announcement found via MindPalette. Thanks for your tireless efforts Nate and Rob!

Tame Dreamweaver’s interface with 5 Tips to Enhance the GL2DW Workflow, see a few common questions about migrating from GoLive to Dreamweaver, do some preflight prep, or troubleshoot your GL2DW Extension Migration Tool here. Currently GoLive CS2 to Dreamweaver CS3 solutions are addressed here. GoLive 9 users: more to come. (I am testing a few legacy sites in GoLive 9 to DW CS3, but I’m not going to make promises I can’t keep). GoLive is dead.

WARNING: Make sure your site file and related folders are backed up before attempting any of these fixes. Some of these work-arounds make permanent changes to the site file.

1. The Snippets/Library Error

JavaScript Error

Script error: Execution halted
In Module: GL2DW
Script File: /Applications/ADOBE CS2/Adobe GoLive CS2/Modules/Extend Scripts/GL2DW/Main.html
At line: 509 :g2dSnippetCounter = traverse (g2dSnippetSourceFolder.ref.getContent(), null);

Find the Extras tab in your site file, and rename the Library item as Snippets.

2. Components to .LBI Issues

WARNING: Make sure your site file and related folders are backed up before attempting any of these fixes. Some of these work-arounds make permanent changes to the site file.

The .lbi files are the Dreamweaver equivalent of a GoLive component. There are multiple reasons why your GoLive components may stall when converting to a library item. Here is one particular problem I have encountered when using the GL2DW extension and a workaround that has been discovered. Currently there is one other solution posted in the Adobe Forums, but it has not helped correct the errors associated my site files. I think the second solution is a stab in the dark, but you can read the discussion for yourself. If I find the second solution does work, I will recreate the error and post it.

JavaScript Error

If you are lucky enough, a JavaScript console will pop up and inform you of a few errors. At first glance, it will look similar to the Snippets problem described earlier.

if (tag) {
var nodeVal = tag.getAttributeNode ('t');
var nodeRef = tag.getAttributeNode ('csref');
if (nodeVal && nodeVal.value = 'Component' && nodeRef) {

The Error Log will read similar to this:

Script error: Execution halted
In Module: GL2DW
Script File: /Applications/ADOBE CS2/Adobe GoLive CS2/Modules/Extend Scripts/GL2DW/Main.html
At line: 334 :if (nodeVal && nodeVal.value = 'Component' && nodeRef) {

The solution, found by John Donaldson:

This is caused by non-component <csobj> elements in component/template files (the GoLive datetime object, older smart rollover objects etc.) The workaround would be to remove GoLive’s proprietary csobj code where it doesn’t specify a component

You can do a Find and Replace to get rid of them:

http://www.afterhours.org.uk/misc/forum/fr.png

Note from the screenshot, you are searching for <csobj> elements whose ‘t’ attribute is NOT component.

John

A small version of his screen shot reposted below.

While the site is open in GoLive, Edit > Find > Find Code Elements… Then for the drop down menus in each section: Element: ls and csobj; Attribute: t and Unequal To and type in “Component” in the third menu; Change: Element: Replace by its Content; Work On: The Extras Tab, then Apply to All. Apply changes to multiple files? Hit Ok.

Results window will pop up. Select all the files, hit Remove. Now run the GL2DW extension again.

Note: This works on the majority of my site files. Some of my older site files (built with GoLive 6 or older, opened and re-saved in GoLive 8 ) still have unresolved errors, and I am constantly looking for other solutions to try as the transition continues.

Seen a bug not mentioned here? Have more questions or any suggestions about the GoLive to Dreamweaver migration? Send it my way: admin@mindgraffiti.net

Did you find this page helpful?

Popularity: 15% [?]