Fireworks cs3 menu & lighbox 2.0 Conflict?

Building on the reports from @pantsonnos and @slovenath and @MidiMagic's note about load-order/globals, here is a compact, practical checklist and fixes that typically resolve Fireworks-exported menu vs. lightbox/overlay conflicts.

• Reproduce on a minimal page and watch the browser console for errors (use Developer Tools / Firebug). JS exceptions often stop subsequent handlers.

• Check for duplicate libraries and load order. If jQuery and another framework are present, call jQuery.noConflict() and use a private alias:

  var $j = jQuery.noConflict();
  $j(function(){ /* use $j(...) */ });

  (see jQuery.noConflict)

• Encapsulate Fireworks-generated code so it does not leak globals. Wrap exports in an IIFE or a namespace before editing:

  (function(){
    // Fireworks code moved here to avoid global names
  })();

• Avoid replacing existing onclick/onload handlers; add listeners instead and stop unwanted bubbling:

  function handler(e){
    e = e || window.event;
    if (e.stopPropagation) e.stopPropagation();
    else e.cancelBubble = true;
    /* handler body */
  }
  if (el.addEventListener) el.addEventListener('click', handler, false);
  else if (el.attachEvent) el.attachEvent('onclick', handler);

  (see addEventListener and stopPropagation)

• Check overlays and stacking: an overlay left visible or with higher stacking context can block menu clicks. Either ensure the overlay is removed/hidden on close, or raise the menu z-index and ensure it has a positioned ancestor:

  #menu { position: relative; z-index: 10000; }

  (stacking contexts explained at Understanding z-index)

• Work on a copy (don't edit original exported file directly — re-exporting will overwrite manual edits).

These steps remove most namespace, event, and z-index problems commonly seen with Fireworks exports and lightbox-style scripts.