IE JavaScript error

Palooka · Post by **Palooka** » Wed Oct 01, 2003 8:19 pm

As you can see here, when any of the main menu items (with the exception of "Our Company") is clicked while using IE, the link does not work due to a JavaScript error. It works fine in other browsers that I have tried. Since the plaintext "Our Company" item link works just fine, I suspect it has something to do with the images. I think this is a brand new bug in the Milonic menus; I wasn't experiencing this problem before I upgraded today. The error states, "_gm is null or not an object." Any input would be appreciated.

Palooka · Post by **Palooka** » Wed Oct 01, 2003 9:39 pm

For those who may be experiencing the same problem, a temporary solution is to simply use the RC 11 version of the mmenudom.js file while continuing to take advantage of improvements in the other RC 13 scripts (particularly the new mmenuns4.js script, which fixes a significant cosmetic issue in Netscape 4).

A question to the Milonic team: would it be possible to provide previous release candidates along with the newest one on the downloads page? I think this would be helpful.

Hergio · Post by **Hergio** » Wed Oct 01, 2003 9:41 pm

IE6, win2k, no errors whatsoever.

Palooka · Post by **Palooka** » Wed Oct 01, 2003 11:23 pm

I, too, am using IE6 on Win2k, and the main menu links generate JS errors without fail.

Post by **John** » Thu Oct 02, 2003 12:14 am

IE6/Win2K here as well, and I am seeing the errors. Looking at the code now.

Post by **John** » Thu Oct 02, 2003 12:26 am

Just a curiosity question while I'm looking. Since you're trying to get the imaged items to do the same thing as you are now doing with Our Company (it appears), why not do them all with text rather than images?

kevin3442 · Post by **kevin3442** » Thu Oct 02, 2003 8:45 am

My two cents...

Using IE6/Win2k, I get the error from any grapical, as opposed to textual, menu item. You'll notice that the same error occurs in the "All Images" sample, both on the Milonic site and in the current downloadable version, suggesting that it's not something in Palooka's code. As Palooka mentioned, replacing RC13's mmenudom.js with RC11's mmenudom.js makes the error go away (don't know about RC12, 'cause I missed that one). Although I wouldn't suggest that as a solution, it does present a clue. Perhaps a bug introduced in RC12 or 13? Figuring out where the bug came in (12 or 13) then comparing that file to RC11's file may yield the answer. I have a utility somewhere that does that... highlighting differences... now if I can only remember what the thing's called and where I put it!

Also, I think it would be a nice touch to make previous releases available -- perhaps not all, but maybe just the more recent ones -- for just such an occasion.

Go to bed John. I see you're currently logged in and it's way past your bed time!

Kevin

Post by **John** » Thu Oct 02, 2003 8:54 am

kevin3442 wrote:Go to bed John. I see you're currently logged in and it's way past your bed time!

Look who's talking

However, I think you hit it right on. Andy will jump on it (he should be getting up about now), if he hasn't already.

Post by **Andy** » Thu Oct 02, 2003 10:05 am

Can somebody tell me what these errors are.

I've tried it in lots of browsers and all seems fine.

Screenshots are good too

Cheers
Andy

4viggo · Post by **4viggo** » Thu Oct 02, 2003 10:24 am

Whenever you click on the "Home" button on your menu sample 18 it shows the following error:

Line: 17
Char: 2680
Error: '_gm' is null or not an object
Code:0
Url: http://milonic.com/menusample.php?sampleid=18

regards
4viggo

Post by **Andy** » Thu Oct 02, 2003 10:27 am

RC14 now contains a fix.

Expect a few more updated later today.

Cheers
Andy

Palooka · Post by **Palooka** » Thu Oct 02, 2003 12:29 pm

Thanks for solving the problem so expeditiously, Andy.

bonewalker · Post by **bonewalker** » Thu Oct 02, 2003 8:37 pm

Here's a new wrinkle: I get a javascript error that says 'Class not defined', and that is all.

I am using RC6, running on IE 6.0 in Win98SE.

I hope to upgrade to the latest RC soon, but I still cannot download anything but the trial version which contains the Milonic link.

This error I mentioned so far has only occured on one users machine, and I cannot reproduce it anywhere else, so it must be something specific to this machine, but I thought I would throw it out here anyway.

Thanks,

Bonewalker

kevin3442 · Post by **kevin3442** » Fri Oct 03, 2003 1:04 am

Bone,

Does your page use any Java applets? If so, are you sure it's a Javascript error and not a Java error? Given the circumstances you described (machine specific) and the error message itself, I couldn't help but wonder.

Kevin

bonewalker · Post by **bonewalker** » Fri Oct 03, 2003 1:19 am

Hi Kevin,

Nope, no Java applets. In fact, nothing on the page but the menu and about a paragraph's worth of text.

That's what is odd about this. I didn't think Javascript supported Classes, but I could be wrong.

Bonewalker

Post by **Andy** » Fri Oct 03, 2003 7:43 am

It's a problem with one of the DLL's on that specific machine.

A re-install of the browser will fix it but I would like to catch this error if possible. Do you have a line number of where the error is.

Cheers
Andy

bonewalker · Post by **bonewalker** » Fri Oct 03, 2003 1:41 pm

Yeah, I feel really useful now!

I will snag the full error and forward it on. Might even get you a screenshot.

Thanks,

Bonewalker

Post by **Andy** » Mon Oct 06, 2003 1:26 pm

This problem is to do with disabled ActiveX.

We've now caught the error and RC15 due out later this week will fix it.

Cheers
Andy

bonewalker · Post by **bonewalker** » Mon Oct 06, 2003 3:05 pm

Excellent Andy!

I hope the error message I sent helped out.

However, I have to tell you that I still cannot download the latest version without the trial Milonic link.

I have emailed someone named Marty about this and not received a reply yet.

Can you help?

Thanks,

Bonewalker
Baker University
License number: 189473

Milonic JavaScript Menu

IE JavaScript error

IE JavaScript error

Different javascript error