Version 5 (Free Menu) Problem...

Red Dalek · Post by **Red Dalek** » Mon Feb 16, 2004 11:34 pm

Hi,

I've been trying to upgrade my version of Milonic Menu so that I can take advantage of the new situation regarding free-site menus without links to Milonic in the menu.

Here is my site using what I preume is version 3 - http://www.dominicself.co.uk and here is my test page using the latest version http://www.freepgs.com/dominicself/test

As you can see there is suddenly a border around the sides of the menu! The only difference I have made to coding is to duplicate my first link (because the forced MILONIC link is still there, how long does it take on average to be recognised btw?) but apart from that the menu_data.js file remains unchanged.

Anyone know how to solve this? Any help much appreciated.

(Oh, and I do feel guilty using the free menu, I will try and buy the licence at some point in the future but as a school student I cannot justify nearly £30 with VAT at the moment for a personal site.)

Post by **Andy** » Mon Feb 16, 2004 11:56 pm

I think the link inside the IFRAME could be the problem.

The link needs to be part of the same page that the menu is in.

Cheers
Andy

Red Dalek · Post by **Red Dalek** » Tue Feb 17, 2004 12:35 am

So is it the Milonic link itself that is causing the strange border???

Post by **Ruth** » Tue Feb 17, 2004 2:16 am

I'm not exactly sure to what your referring since you have border set to show, and it shows in both versions on all the browsers I tried. Do you mean the open space after the separator bars on the right? That's because of the overflow="scroll"; that space is where the scroll bar appears if needed, if you remove that you'll see the menu looks normal. Also, in your data file you have in the style declaration screenposition="center"; and then in the menu you have a top and left listed and position="relative"; I don't know if they will cause a conflict or not. Also, the top of the data file has the usual _menuCloseDelay=500 etc. but then at the bottom of it, there is this

Code: Select all

drawMenus();
_menuCloseDelay=500;
_menuOpenDelay=150;
_scrollAmount=3;
_scrollDelay=20;
_followSpeed=5;
_followRate=40;
_subOffsetTop=0;
_subOffsetLeft=0;

drawMenus();

this is the menu_datanew.js file

Ruth

Red Dalek · Post by **Red Dalek** » Tue Feb 17, 2004 11:30 am

Thank you soooo much! I luv u Ruth!

All I need to do now is get the Milonic link inside the actual page...

Post by **Ruth** » Tue Feb 17, 2004 9:36 pm

Well, just get one of the little buttons on Milonic and put an html link in

Unless you mean get it out of the menu. That requires you get a license, that is you request a license for free site. If you qualify then you'd get a notice and download the menu again and get one without the link.

Ruth

Red Dalek · Post by **Red Dalek** » Tue Feb 17, 2004 10:05 pm

Actully, if you include a link to Milonic in your HTML the forced link disappears..

Post by **John** » Tue Feb 17, 2004 10:47 pm

With the apparent exception of NS right now...

Red Dalek · Post by **Red Dalek** » Tue Feb 17, 2004 11:06 pm

Ur... sorry I don't understand?

allgoodpeople · Post by **allgoodpeople** » Tue Feb 17, 2004 11:37 pm

Red Dalek wrote:Ur... sorry I don't understand?

I had posted earlier today that the forced link isn't being removed in Netscape 7.1, even when a link to milonic.com is included in the page. Not sure if this is just an issue with my page or a general issue with the menu though. I think that's what jgillet was referring to.

Mark

Red Dalek · Post by **Red Dalek** » Tue Feb 17, 2004 11:40 pm

[joke] I see... well if you will insist on using Netscape

[/joke]

allgoodpeople · Post by **allgoodpeople** » Tue Feb 17, 2004 11:46 pm

Red Dalek wrote:[joke] I see... well if you will insist on using Netscape [/joke]

*lol* it's not ME who insists on using it!!

I'd be just as happy if I didn't have to try to get my site to work correctly on 4 different browsers. But until you and I get everyone to agree on one browser (or the browsers start rendering the same code the same way), guess we're stuck.

Mark