Back To Start Of Archive
Taken From The Forum: Help & Support for DHTML Menu Version 5+
Forum Topic: Click to view post
Last Updated: Saturday July 14 2012 - 06:07:12
JavaScript errors after upgrading from Version 5.3 to 5.44
Poster: tiffanyaward
Dated: Monday August 30 2004 - 17:20:02 BST
Hi. I am receiving JavaScript errors after upgrading from V5.3 to V5.44. I call the drawMenus() function from within a table in my HTML code. I updated the mmenudom.js and the milonic_src.js files, but haven't touched the code in my menu_data.js file. However, even when I replace my menu_data.js file with the one provided in the updated version, I still get the errors. I get "'_n' is undifined" which is referring to this line in mmenudom.js: "Type Professional*/_dBT=_n;_dBL=_n;". I also get "'mm_style' is undefined" which is being called from my menu_data.js file. My code is written in Lotus Domino forms, and I am using IE 6 as my browser. Also we are using the professional, purchased lincense version. As I mention above, I haven't had any problems until upgrading from 5.3 to 5.44. Please let me know if you have any suggestions.
Thanks,
Tiffany Ward
Poster: perldev
Dated: Monday August 30 2004 - 17:34:58 BST
Since you didn't change the name of milonic_src.js and mmenudom.js, they could be cached. Clean up your cache, and try again. or append a ? +timestamp at the end of script src.
Good luck
Re: JavaScript errors after upgrading from Version 5.3 to 5.
Poster: kevin3442
Dated: Monday August 30 2004 - 19:16:06 BST
Hi Tiffany,
tiffanyaward wrote:
...I updated the mmenudom.js and the milonic_src.js files, but haven't touched the code in my menu_data.js file....
It's true that you typically do not need to replace your menu_data.js file when updating. However, you do need to upload the new version of milonic_src.js. If I read your message literally, you only uploaded the new versions of mmenudom.js and mmenuns4.js. That's good, but you also need to upload the new milonic_src.js; so there are three files that need to be updated: milonic_src.js, mmenudom.js, and mmenuns4.js.
Cheers,
Kevin
JavaScript errors after upgrading from Version 5.3 to 5
Poster: tiffanyaward
Dated: Monday August 30 2004 - 20:13:45 BST
I cleared my cookies and temporary internet files, but still get the same errors. "'_n' is undifined" which is referring to this line in mmenudom.js: "Type Professional*/_dBT=_n;_dBL=_n;" and "'mm_style' is undefined" which is being called from my menu_data.js file. I have updated all three source files to version 5.44, and replaced the menu_data.js file (just to eliminate that as a problem), but I continue to get the errors. I also tried renaming the source files, and no luck there either. When I replace the files with the ones from Version 5.3, everything works great again. What else could it be? I appreciate your help.
Thanks,
Tiffany
Poster: Ruth
Dated: Monday August 30 2004 - 20:43:16 BST
Do you have a url we can check? It's hard to figure out without seeing the problem, and what browser and OS?
Ruth
Poster: tiffanyaward
Dated: Monday August 30 2004 - 21:37:33 BST
It's on our intranet right now, so you won't be able to get through. I'm going to check with my boss about putting it on an external server so that I can troubleshoot easier with you. Are there any problems with excluding the mmenuns4.js file? We haven't been calling it in our menus b/c everyone is on at lease IE5. I'm using WinXP SPK1 and IE6. Also, I am calling the drawMenus() function from within a table in my HTML instead of leaving it in the menu_data.js file. Would that cause a problem with the new version?
Thanks,
Tiffany
Poster: Ruth
Dated: Monday August 30 2004 - 23:20:06 BST
Actually, you wouldn't need to put the whole site up, you just need to put up a page which is throwing the errors if we can't solve it without seeing the page. Make sure you haven't changed anything in the 3 menu files. You might also try downloading the files again in case there was some corruption on the first download. You mentioned it being in a table, you need to make sure you have put it in the table per directions for that. I believe they show the drawmenus in both the table cell with the main menu and in the menu_data.js file. I'm not sure about the mmenuns4.js, you might insert that and see if it makes a difference.
Ruth
Here's a link to the problem
Poster: tiffanyaward
Dated: Wednesday September 29 2004 - 21:07:54 BST
I know it's taken me a month, but I finally got a test site up for you guys to view. Just to recap my problem, we are using the lincensed menus in a Lotus Domino Application. Everything has worked great up to version 5.3, but nothing after that will work. This link will take you to a page that shows the menus using script files from V5.3, and another link using script files from V5.44, which throws up JavaScript errors. I am using the milon_data.js version 5.44 file for both apps. The links go to two separate Domino .nsf databases, so they are calling completely different source files. I haven't changed any names or code, yet version 5.44 will not work. In order to view the page, you will need to login as user: test password: test1964
Heres the URL:
https://intranet.laynechristensen.com/milonic-test.nsf
Thanks for your help!
Tiffany Ward
Poster: John
Dated: Wednesday September 29 2004 - 21:22:04 BST
Tiffany, you have messed with the menu code files. Shame...
milonic_src has been compressed, and shows up here as completely commented out! In mmenudom you have completely removed the copyright notice (a legal no-no), and possibly compressed that file as well.
Get a fresh download (we're up to 5.48 now, anyway), and upload the files as received - no messing around.
Let us know how it goes.
Maybe you don't know how Domino Scrip files work....
Poster: tiffanyaward
Dated: Wednesday September 29 2004 - 21:45:10 BST
Maybe you don't know how Domino Scrip files work....Domino designer has a section called "Script Libraries" under "Shared Code". Anytime you want to create a javascript source file, you have to create a new Javascript library and past in the code from a text file (in this case, the text files downloaded from the .zip). Unfortunately, it pastes the code in as one long sting with no breaks. In the first one (5.3), I went in and physically added in breaks to make the file readable which took about an hour. I don't have the kind of time, so I just leave it as one long string in the src file. If you know of a more efficient way of handling this in Domino, I'm all ears. I don't know what you're looking at, but the code is all there. I could care less about copyright info and have no desire to remove it. Oh, I pasted in the code from the new 5.48 src files (mmenudom.js and milonic_src.js) and I get the same errors. Thanks for your help.
Tiffany Ward
Nevermind....I fixed my own problem
Poster: tiffanyaward
Dated: Wednesday September 29 2004 - 22:02:44 BST
Nevermind....I fixed my own problem. If you open the files extracted from the .zip with Notepad, it can't read some of the characters and it displays the code in with no breaks. Therefore, I had been pasting it with bad code into my Domino script files. However, that doesn't explain why 5.3 worked and none of the others did. When I open the files with WordPad, it reads everything correctly and leaves most of the breaks. Because it's reading correctly, I can paste it correctly into the Domino Javascript Library in Notes. Now it works. I'm NOT changing code either...I can barely read it. Thanks anyway.
Thanks,
Tiffany