MenuMachine 2 only
GoLive CS, CS2
Article ID: 000145
Category: Browser Issues
I have been told to upload to the public_html, www, htdocs or similar special folder on my web host server. When I create this folder in my GoLive site, I cannot edit my menus or see them in the MenuMachine 2 Objects Palette. The menumachine folder is created at the folder level above the index page.
I either see the "No menus are defined in this site" message in the Object Palette or my menus don't work correctly online.
If you have been told to upload to a particular folder on the server, this should be set up in your site upload settings. You do not need to create this folder in your site. In fact, to do so will cause problems. The top level (root) of your GoLive site should be the folder that contains your index page.
What you see in the left pane of your site window should mirror what you see inside the public_html folder on the server. This means you should not have a public_html folder in your GoLive site.
Note: in this article, we use the name "public_html" for the special folder on the server, however it may be called "www", "htdocs", "mainwebsite_html" or other names, depending on your server configuration. Simply substitute the name of your special folder when you see public_html below.
A correct site and server setup
In the image below, the site hase been structured correctly in GoLive. The index page, GeneratedItems folder and menumachine folder are correctly located at the root level of the site. They are not buried inside another folder. On the Publish Server, the files are in the same order, inside the public_html folder. Inside the public_html folder are some additional files/folders which should not be removed or renamed. (These server files are not required in the local GoLive version of the site}.
In this article, you will learn how to achieve the correct site structure and how to set your site upload setting so that you will always login to the correct folder on your server.
NOTE: This article requires that you make major changes to your site. Please make a full backup of the entire site project (not just the .site file) so that if anything goes wrong, you can go back to the old site.
How the local site should look in GoLive
It is important that your local site (what you see in the left pane of the GoLive site window) looks similar to this even if you have been told to upload to the public_html folder on your server:
How to change the site upload settings
If you have been told to upload to the public_html, www or another folder on the server, you need to change your upload settings so you automatically upload into that folder.
Open the site and go to Site > Settings.... Click on Publish Server in the list on the left of the Settings window. Set up your login details as supplied by your web host.
To select the specific folder you have been told to upload to, click on the Browse button next to the Directory field:
You will then be logged in to the server and you will see a list of files and folders on the server. Locate and open the folder to which your host has told you to upload. e.g. public_html.
In the image below, we have opened the public_html folder. There may be some files in there that you do not recognize. Do not move, delete or rename these files on the server. Once you are inside the correct folder, click on the OK button.
You then are returned to the Settings window and the path to the public_html folder has been added to the Directory field. Click OK to save the site settings:
Now, whenever you login to the server, you will be taken directly into the correct folder. You can the path to the folder in the Publish Server Tab in the site window below:
Correcting the site structure in GoLive
If you have already created a public_html folder or www folder in your local site, you should remove this folder to restore the correct file structure.
In the image below, the site contents have been moved into a public_html folder. This public_html folder is not required and should be removed:
Having the index page, the GeneratedItems folder and the menumachine folder buried inside another folder will cause problems. GoLive and MenuMachine will not know that you intend the root of the site to be inside the public_html folder.
GoLive and MenuMachine understand the root level to be the first level within the web-content folder. MenuMachine is looking for the menumachine folder at the root level of the site. If it can't find it there, you will see a message in the Objects Palette "No menus are defined in this site" as in the image below:
You will need to move the contents of the public_html folder back to the proper root level.
In the image below, you can see that the entire contents of the public_html folder have been selected and are being dragged. Drag the files/folders to the Name heading in the site window as shown. This moves them to the level above the public_html folder:
Because you are moving files to a new directory, GoLive will prompt you to update the files. You need to allow GoLive to update the links in the files so they are correct once moved. Make sure all the files are checked as in the image below (you may have more files in your list but they must all be checked):
When the public_html folder is empty, delete it. Your file structure should then look similar to the image below with the index page, the GeneratedItems folder and the menumachine folder back at the root level:
How to retrieve your MenuMachine menus
To get your MenuMachine 2 menus back in the list in the MenuMachine 2 Objects Palette, click on the Refresh List button. MenuMachine will then attempt to find the menumachine folder at the root level of the site. It will display a message like this:
If you have correctly moved the menumachine folder, MenuMachine will find your menus:
If MenuMachine can't find the menus, your site structure may still not be correct. Please review this article again to make sure you have set up the site correctly.
If you cannot fix it, send your site to support.
See Article 000141 for Mac instructions.
See Article 000140 for Windows instructions.
Last updated: February 24, 2008
This article has been viewed 36122 times.