Bug symbol on the menuspecs.js file or menuspecs_preview.js file (MM2)
Article Applies To:
MenuMachine 2 only
GoLive CS, CS2
Mac, Windows
Article ID: 000112
Category: General Issues
Issue
The menu seems to be working OK but GoLive is flagging the menuspecs.js and/or menuspecs_preview.js files in the menu folder with a bug icon. Why is this happening?
Solution
The menuspecs.js file contains the links that you have assigned in your menu. These may be links to images or links to pages.
Bug seen next to menumachine folder indicates problem in a file…
Firstly, close the MenuMachine 2 Editor so you know you have saved the menu and your recent edits have been saved.
Open the menumachine folder and then open the folder which relates to the problem menu to see which file/s are affected.
Three files in this folder have a bug symbol…
If you have a bug symbol on the menuspecs.js file in your site, there could be a problem with the menu when it is uploaded.
To identify the problem link/s, open the In & Out Links Palette.
Click once on (do not open) the menuspecs.js file and it will appear in the In & Out Links Palette. The files to the right of the menuspecs.js file are the links the file contains. If any are marked with a question mark (?) symbol, they are broken.
The menuspecs.js file is selected and showing in the In & Out Links Palette. Two files show the incorrect link symbol. MenuMachine can't find these files in the site.
If you know what those links are supposed to be, open the menu in the Menu Editor and re-link them using the pick-whip.
Alternatively, you can fix the links using the In & Out Link Palette. Use the pick-whip next to the problem link to link to the correct file in your site. Repeat for any other problem links in the menuspecs.js file.
The file called index1.html does not exist in the site. It should be linked to index.html instead…
After relinking, you will notice that only the menuspecs.js file is fixed. Open the menu in the MenuMachine 2 Editor and make a small change and then re-save the menu. The navigation.html file will be corrected.
What about the menuspecs_preview.js file?
The menuspecs_preview.js file is created when you preview a menu while you are working in the Menu Editor. It is only created or updated when you press the Preview Tab* in the Menu Editor.
If you last previewed the menu while the menu still had the broken links, the bug is shown on the menuspecs.js file.
This file is not referenced when the site is published and it is just a sort of a temporary file used internally for MenuMachine. You can either ignore it or, if it bothers you, just open the Menu Editor and click on the Preview Tab to generate a new menuspecs_preview.js file for that menu. Repeat for any other menus in your site which have a bug on that file.
As long as you don't have a bug on the menuspecs.js file, the menu itself is correct. The navigation.html file is the site map your visitors see if they have JavaScript disabled in their browser so you should make sure it has been corrected as well. When you next upload the menumachine folder you will see your corrected menu online.
*NOTE: The bug does not disappear on the menuspecs_preview.js file immediately when the Preview Tab is used. However, if you open the menuspecs_preview.js file the links have been corrected and then on closing the file the bug disappears. GoLive needs some "intervention", like the file being opened, before changing the bug status.
Similarly, if you delete the menuspecs_preview.js file and use the Preview Tab, you need to refresh the site window before GoLive "sees" the newly-created menuspecs_preview.js file.
Last updated: March 14, 2007
This article has been viewed 5239 times.