Menu Writer not working with Visual Lightbox

I am using CSS menu writer on a page with a photo album created with Visual Lightbox. Everything works fine except when you click on an image and the image pops up, fading out the background and centering on the page, the menu stays on top instead of staying in the background (like the rest of the page). I'm sure it's just a setting that I'm missing.

Thanks,

Please post a link where i can investigate the issue.

Here is the link:

photos.html

I am viewing this on a PC with FireFox.

in the menu.css file, change:
ul#cssmw li {
background-image: none;
float: left;
padding: 0 0 0 0;
position: relative;
white-space: nowrap;
z-index: 100;
}



to:
ul#cssmw li {
background-image: none;
float: left;
padding: 0 0 0 0;
position: relative;
white-space: nowrap;
z-index: 1;
}

Perfect! Thanks for the quick reply.

I might have spoken too soon. Now when I tried to make a change to the menu, I got this error when I click OK (after making the changes):

Error generating menu (wa.generate.menu):
TypeError: MM.SA_createProcessingObject is not a function

try deleting the Dreamweaver cache file from the users configuration folder:
common_installation_issues.pdf

Why is this required so often when using webassist extensions? It seems that this is the first answer to many error messages. The css menu writer was working fine, I made that one tiny change that you suggested (changing z-index: 100; to z-index: -1;) and then I have to delete the dat file. I had to do this same thing when I ran into an error with the form builder also. It's obviously so common, that you have it listed at the top of this page as a notice.

the Dreamweaver cache file is susceptible to becoming corrupted, any time a behavior is run in Dreamweaver, the behaviors code is compiled and stored in he dat file, this is an attempt by Dreamweaver to speed things up the next time that the behavior is run. That compiled behaviors can become unstable though quite easily and cause random errors to start occurring.

Deleting that file is always the first step in troubleshooting error messages in Dreamweaver.

Adobe has it listed at number 4 in their troubleshooting guide:
kb405604.html

but it is one of the simpler things to try, so I always try it first.