Declaring scriptpath in milonic_src.js

Poster: tepidarium
Dated: Tuesday October 21 2003 - 15:03:39 BST

Hi all,

I have read the FAQ on the Milonic website and it says you can declare the scriptpath in milonic_src.js to allow for using absolute referenced urls -i.e. "/menu/menu_data.js"

I would like to do this as currently I am using "http://www.mydomain.com/menu/menu_data.js"

Where in Milonic_src.js should one make the change? I could not find the scriptpath variable, so I decalred one about the other commands...but this doesn't work.

Thanks for any help you can provide!

Poster: John
Dated: Tuesday October 21 2003 - 15:22:47 BST

Scriptpath is no longer used or defined. Has not been for quite a few releases. Check the docs that come in the download for the proper setup and calls.

Poster: tepidarium
Dated: Tuesday October 21 2003 - 15:53:06 BST

Hi,

Thanks for your resposne. I have reread: readme.txt, install.txt, howtobuild.txt - I cannot find information detailing change of script path. At this point I am unable to get absolute scriptpaths to work with the menu when the paths beign witha forward slash i.e. "/menu/menu_data.js" will not work while defining "http://www.mydomain.com/menu/menu_data.js" will work.

Poster: John
Dated: Tuesday October 21 2003 - 15:58:23 BST

URL?

Poster: tepidarium
Dated: Tuesday October 21 2003 - 16:05:30 BST

Hi john -

The url is:

http://www.citytech.cuny.edu/m-menu.html

It works when I uploaded the file to the server, but won't work locally on my c: drive. The file path is the same.

Thanks

Poster: John
Dated: Tuesday October 21 2003 - 16:15:52 BST


Ah - now you tell me that

If it works on the server but not locally there has to be a difference in the pathing. They may look the same, but often it's a real bear to get a local setup to operate properly. My menus won't work locally either, but the problem there is all of my directories are virtual and I'm tired of the headaches in trying to figure out what will work in both places while keeping the pathing as clean as possible and keeping the Dreamweaver site manager happy as well.

Poster: tepidarium
Dated: Tuesday October 21 2003 - 16:22:40 BST



Ok, I'll guess I'll jut have to live with not seeing the menus locally. Is there any advantage to declaring the absolute server path i.e., "http://www.mydomain.com/menu/menu_data.js" ?

On an unrelated issue, I'm hoping for a hide object fix before I implment the menu system site wide so I can keep my flash scroller where it is (for NS 4 & IE 5 & Opera 5)

Poster: John
Dated: Tuesday October 21 2003 - 20:31:14 BST


I don't think so.


That would be Uncle Andy's department. He's been sick, but last I heard he's still alive.

Poster: Hergio
Dated: Tuesday October 21 2003 - 22:46:48 BST

Andy informed us that he's "cracked the hide div problem" so you may see something soon that may be able to hide your objects.

Absolute pathing has NO disadvantages in regards to addressing. It will however clutter your source code slightly and will increase the file size of your page. This isn't considerably bad as long as you dont have a page with 500 links on it, ya know what I mean? The advantages of the absolute addressing is just that, its absolute, so you can use it in any page and be assured it will work. Best of luck!

Poster: tepidarium
Dated: Wednesday October 22 2003 - 4:13:52 BST



Awesome...I'm looking forward to it!



Would you say there is any particular benefit for using this absolute style:

"http://www.mydomain.com/menu/menu_data.js"

over this absolute style:

"/menu/menu_data.js"
?

John thought no.

Poster: John
Dated: Wednesday October 22 2003 - 4:54:18 BST


Just to be picky, the first one is absolute, the second is server-relative. Assuming identical pathing, server-relative makes a site move from one server to another a no-brainer. For instance, we develop on http://webdev..., but our production server is http://westcgi... . With server-relative the move is made with no code or path changes at all. If you used absolute, all URLs would have to be changed site-wide.