I just purchased and installed Milonic menus.
I copied the 4 .js files to my server site to a directory called "menus".
I edited the paste-in code to have "menus/" prior to each .js filename.
I put the code into a file http://www.willowbrook.org/menus/testmenus.htm
The menus aren't appearing.
Menu won't appear
-
annasue
- Super Advanced
- Posts: 42
- Joined: Thu Apr 14, 2005 11:37 pm
- Location: Huntsville, AL
- Contact:
Menus not appearing
Thanks, Kevin, the /menu/ did the trick. I'm sure the first suggestion would have worked also.
I'm excited about using this product.
Anna sue
I'm excited about using this product.
Anna sue
Hi Anna Sue,
Just to clarify, the two suggestions are pretty much the same thing. The problem was that menus/ is a "document relative path", essentially telling the browser to look for a folder named "menus" within the folder that the htm document was loaded from. So, by having your testmenus.htm file in the "menus" folder, the document relative path to your .js files ended up being "http://www.willowbrook.org/menus/menus/". By placing a / as the front of the path name, i.e., /menus/, you tell the browser that you want to use a "root relative path", i.e., it's relive to the root or "starting point" of your site, which in your case is http://www.willowbrook.org/ . So, by using /menus/ you're telling the browser that, no matter where the currently loaded document came from, look for the file in the /menus/ folder that branches off of http://www.willowbrook.org .
You can also use an absolute path, which includes the domain name. For example, the absolute path to your "menus" folder is http://www.willowbrook.org/menus/ .
You'll find that the terminology will vary, depending on who writes about relative vs. absolute paths. But it's the concept that's important to understand. Here's a good discusison of paths:
http://www.communitymx.com/content/arti ... ?cid=230AD
Cheers,
Kevin
Just to clarify, the two suggestions are pretty much the same thing. The problem was that menus/ is a "document relative path", essentially telling the browser to look for a folder named "menus" within the folder that the htm document was loaded from. So, by having your testmenus.htm file in the "menus" folder, the document relative path to your .js files ended up being "http://www.willowbrook.org/menus/menus/". By placing a / as the front of the path name, i.e., /menus/, you tell the browser that you want to use a "root relative path", i.e., it's relive to the root or "starting point" of your site, which in your case is http://www.willowbrook.org/ . So, by using /menus/ you're telling the browser that, no matter where the currently loaded document came from, look for the file in the /menus/ folder that branches off of http://www.willowbrook.org .
You can also use an absolute path, which includes the domain name. For example, the absolute path to your "menus" folder is http://www.willowbrook.org/menus/ .
You'll find that the terminology will vary, depending on who writes about relative vs. absolute paths. But it's the concept that's important to understand. Here's a good discusison of paths:
http://www.communitymx.com/content/arti ... ?cid=230AD
Cheers,
Kevin