Ver5 loads very slow in IE7

[Andy]

What can I say?

Imagine our frustration when another company provides a product that ultimately causes our product to fail through no fault of our own. The time I have spent on this issue alone has been immense.

Now, the problem is that I do not and cannot obtain a copy of the faulty version of NIS for testing. The only version I can get is the latest from the Symantec website and that version has been fixed.

If somebody is prepared to let us have a copy of NIS that breaks I'll gladly do what I can but so far nobody has offered us a copy. All our attempts at contacing Symantec for a copy have failed. They are just like Apple - couldn't care less about us.

My hands are tied on this one. It's most definitely NOT our fault but boy is it our problem

Cheers,
Andy

[steve.n]

Andy,

I should have an old version backed up somewhere - it will be registered to me but I trust you

Give me an email address and I'll send it to you. These kind of problems are a real pain - good luck and keep us informed.

Steve

[Andy]

Hi Steve,

Can you please send it to my forum username at forum domain name - you get the the idea?

-- Andy

[Andy]

Thanks for sending me the copy of NIS, Steve - I managed to install a 15 day trial so won't need a key just yet.

Unfortunately, as I expected, everything runs fine - I see the milonic.com site appear in about 2 seconds, that's just typical.

The ONLY way I'm going to be able to debug this is if somebody gives me remote control of their PC - and that's never going to happen. Or, if somebody can find why some machines work and others do not.

I honestly do not know what to suggest now - I'm DESPARATELY trying to get the new version of the menu ready but I'm snowed under with support and other issues like this. The new menu does not exhibit any issues.

Anyway, I've just spent 3 hours trying to debug another users menu only to find they had made changed to the menu code ARGHHHHH!!!! - I'm having a very bad year. Roll on 2009

[Andy]

is http://milonic.com/ any better?

[steve.n]

Hi Andy

Well at least that does narrow the problem - I'll need to set up another PC to test this as I have V16 instaled now.

Steve

[rudy]

Were you able to see if version 5.808 fixed the problem that caused pages with the Milonic menu on them and using IE7 and also an older version of Norton Internet Security to open very slowly?

Thanks for working on this!

[Konrad]

Here is a Quick Solution for this problem and it works fine with all versions of Norton Confidential Browser Helper Object

At the end of your mmenudom.js file you have a code something like this:

Code: Select all

write("<iframe class=mmenu FRAMEBORDER=0 id="+$mV+_p5+" src='javascript:false;' 

Remove this one :

Code: Select all

src='javascript:false;' 

So you should have now :

Code: Select all

write("<iframe class=mmenu FRAMEBORDER=0 id="+$mV+_p5+" 

That's it

[steve.n]

aha - thanks, Konrad. I can't test it right now as I'm running a different ver of Norton but how did you figure it? Very curious

[Andy]

The above will work on non secure pages. It will also work if you add: _CFix=true; to the top of your data file.

The problem is that Internet Explorer 6.0 requires a link within an IFRAME or else it spews a security warning.

[rudy]

I'm a bit confused now. So Andy, are you saying Kevins code will fix the NIS slow loading issue on some older versions, but by applying his fix it will cause a security warning for IE 6.0 users?

The above will work on non secure pages. It will also work if you add: _CFix=true; to the top of your data file.

The problem is that Internet Explorer 6.0 requires a link within an IFRAME or else it spews a security warning.

[Konrad]

aha - thanks, Konrad. I can't test it right now as I'm running a different ver of Norton but how did you figure it? Very curious

I'm using Milonic Menu on my site - and my customers complained so I found out that internet explorer have problems in generating iframe instances when data is resent to a webpage - and Norton Confidential Browser Helper Object causes the data to be resent and thats why it lags

The above will work on non secure pages. It will also work if you add: _CFix=true; to the top of your data file.

The problem is that Internet Explorer 6.0 requires a link within an IFRAME or else it spews a security warning.

Yes - only on sites with SSL. However instead of :

Code: Select all

write("<iframe class=mmenu FRAMEBORDER=0 id="+$mV+_p5+" src='javascript:false;' 

you can use:

Code: Select all

write("<frame class=mmenu FRAMEBORDER=0 id="+$mV+_p5+" src='javascript:false;' 

so everything should work fine

[Konrad]

I'm a bit confused now. So Andy, are you saying Kevins code will fix the NIS slow loading issue on some older versions, but by applying his fix it will cause a security warning for IE 6.0 users?

Dude thats not my name

[Andy]

I'm a bit confused now. So Andy, are you saying Kevins code will fix the NIS slow loading issue on some older versions, but by applying his fix it will cause a security warning for IE 6.0 users?

The above will work on non secure pages. It will also work if you add: _CFix=true; to the top of your data file.

The problem is that Internet Explorer 6.0 requires a link within an IFRAME or else it spews a security warning.

If all you want to do is fix the slow loading of the menu re: NIS - then add _CFix=true; to the top of your menu_data.js file.

The security warning will only appear on secure sites under https - none secure sites will not be affected

[rudy]

Sorry, thought I was responding to Andy

I'm a bit confused now. So Andy, are you saying Kevins code will fix the NIS slow loading issue on some older versions, but by applying his fix it will cause a security warning for IE 6.0 users?

Dude thats not my name

[rudy]

Will this fix for the NIS issue be in point version fix?

I'm a bit confused now. So Andy, are you saying Kevins code will fix the NIS slow loading issue on some older versions, but by applying his fix it will cause a security warning for IE 6.0 users?

The above will work on non secure pages. It will also work if you add: _CFix=true; to the top of your data file.

The problem is that Internet Explorer 6.0 requires a link within an IFRAME or else it spews a security warning.

If all you want to do is fix the slow loading of the menu re: NIS - then add _CFix=true; to the top of your menu_data.js file.

The security warning will only appear on secure sites under https - none secure sites will not be affected

[Konrad]

Sorry, thought I was responding to Andy

no problem

[rudy]

When placing the _CFix=true; in the top part of my menu_data.js file I noticed that the other entries didn't use a (;) semi-colon at the end, as shown below. Is that semi-colon necessary for it to work?

Code: Select all

_CFix=true;
_menuCloseDelay=500           // The time delay for menus to remain visible on mouse out
_menuOpenDelay=150            // The time delay before menus open on mouse over
_followSpeed=5                // Follow scrolling speed
_followRate=50                // Follow scrolling Rate
_subOffsetTop=5               // Sub menu top offset
_subOffsetLeft=-1             // Sub menu left offset
_scrollAmount=3               // Only needed for Netscape 4.x
_scrollDelay=20               // Only needed for Netcsape 4.x
buildAllMenus=true

If all you want to do is fix the slow loading of the menu re: NIS - then add _CFix=true; to the top of your menu_data.js file.

The security warning will only appear on secure sites under https - none secure sites will not be affected[/quote][/quote]

[rudy]

Hi Andy,
Is this the section of the menu_data.js file that the _CFix=true; code should be added? See code below:
Should it be added as _CFix=true or _CFix=true; (with the semi-colon at the end_

Code: Select all

_menuCloseDelay=500           // The time delay for menus to remain visible on mouse out
_menuOpenDelay=150            // The time delay before menus open on mouse over
_followSpeed=5                // Follow scrolling speed
_followRate=50                // Follow scrolling Rate
_subOffsetTop=5               // Sub menu top offset
_subOffsetLeft=-1             // Sub menu left offset
_scrollAmount=3               // Only needed for Netscape 4.x
_scrollDelay=20               // Only needed for Netcsape 4.x
_CFix=true
buildAllMenus=true

I'm a bit confused now. So Andy, are you saying Kevins code will fix the NIS slow loading issue on some older versions, but by applying his fix it will cause a security warning for IE 6.0 users?

The above will work on non secure pages. It will also work if you add: _CFix=true; to the top of your data file.

The problem is that Internet Explorer 6.0 requires a link within an IFRAME or else it spews a security warning.

If all you want to do is fix the slow loading of the menu re: NIS - then add _CFix=true; to the top of your menu_data.js file.

The security warning will only appear on secure sites under https - none secure sites will not be affected

[Andy]

Hi Rudy,

Looks good to me.

Regarding the semi-colons: With JavaScript (unlike other languages like PHP) the semi-colon is not required if there is a carriage return. It's only there to keep things looking right. I'm sometimes sloppy in the demos but I'm working on fixing things for the new version of the menu.

So to sum up - semi colons are not always needed in JavaScript providing you are separating code with carriage returns

-- Andy