Industrial Strength JavaScript and DHTML Menus
About Us
Testimonials
Contact Us
Our Distinguished Clients
Investing in Non-Profits
Where Are We
Privacy Policy
Software Licensing Agreement
DHTML JavaScript Menu
Product Information
Page Integration
Quick Reference Guides
Embedding Into a Table or DIV
Purchase
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:08
Menu not showing up...
Poster: nbozic
Dated: Tuesday September 28 2004 - 21:09:01 BST
The menu seems to work great on most operating systems and most browsers. However, it doesn't show up at all if the operating system is Mac OS X (.3.5) while using either MS Explorer 5.2.3 or Safari 1.2.3 browsers.
It does work great on lower versions of Mac OS...
What could be the reason why the menu doesn't show up?
Thanks,
NB
PS: We're using the latest version of Milonic DHTML menu - I just installed it a couple of days ago. http://www.greaterlouisville.com
Poster: John
Dated: Tuesday September 28 2004 - 22:29:48 BST
Don't know about IE (dumped that piece of junk), but I'm looking at all kinds of menus and sub-menus on chamber.asp right now under Safari. I don't see any problems at all. 10.3.5/1.2.3 (v125.9).
Poster: nbozic
Dated: Wednesday September 29 2004 - 13:30:16 BST
This is very odd. I saw it for myself - there were no menus at all on that machine. I have no idea what it is...
Is it possible that there are some settings (javascript, security,...) that could prevent the menus from showing up with MAC OS X?
Poster: John
Dated: Wednesday September 29 2004 - 14:46:29 BST
I doubt security, but JS can be turned off in Safari.
Are all updates installed? A new JS came out last week.
Poster: nbozic
Dated: Wednesday September 29 2004 - 21:21:38 BST
Yes, I think all updates are installed.
I'm starting to think that this whole thing may be an isolated issue... After all, my co-worker checked the web site at his house, and it worked fine (although he used the exact same operating system and exact same browsers - the problem didn't persist at home). There may be something wrong with his machine at work...
Thanks,
NB
Poster: John
Dated: Wednesday September 29 2004 - 21:24:18 BST
Given that it's only happening on one machine, I would tend to agree with you. Let us know if you find out anything else.
Poster: Maz
Dated: Wednesday September 29 2004 - 23:08:21 BST
What am I looking at? Is it the image map? I like that, very nice.
Maybe its the slow loading, I'm on modem.
Okay now I go to 'Living in ...' and there is a horizontal menu.
What menu should I be looking for ... in Safari?
maz
Poster: Ruth
Dated: Wednesday September 29 2004 - 23:33:44 BST
It's flash, but I really like the look. Even if it does load slow
Ruth
Poster: John
Dated: Thursday September 30 2004 - 0:04:21 BST
Maz wrote:
What menu should I be looking for ... in Safari?
Any Milonic menu (once you get by the Flash). One of his customers was saying he got no menus at all.
Poster: Maz
Dated: Thursday September 30 2004 - 1:28:06 BST
The horizontal menu I found on other pages was not on the first page, is that where its supposed to be? Then maybe its slow modem load with flash causing the problem. But since the flash loads it has a menu, so I'm not sure.
maz
Poster: John
Dated: Thursday September 30 2004 - 3:57:01 BST
There is no other menu programmed for the Flash page (that I could see).
Poster: nbozic
Dated: Thursday September 30 2004 - 13:51:16 BST
It's the menu that you see when you click on the "chamber home" tab. In one persistant instance (on one machine that has mac os x) the menu is not there at all... basically it looks like the page you see when you click on the "community home" tab - no menu at all. Community home is not supposed to have a menu, but chamber home is.
I'm wondering if most people who use mac os x can see the menu, which would be desirable and the current issue would be an isolated incident.
Poster: Maz
Dated: Thursday September 30 2004 - 18:13:14 BST
No problem here then, maybe check the settings for js or the js update was not completed correctly.
maz
Poster: John
Dated: Thursday September 30 2004 - 19:54:53 BST
I've now looked at it on two different systems from two completely different locations. Still no problems.
Poster: kevin3442
Dated: Friday October 1 2004 - 1:02:00 BST
I've just had time for a quick look. I don't have a mac to test with, but I'd suggest making a few changes in the following lines where you load the menu files:
Code:
<script type="text/javascript" Language="JavaScript 1.3">
function search()
{
if (document.searchform.elements["zoom_query"].value == "") {
alert("Please enter a word or phrase to search for.");
document.searchform.elements["zoom_query"].focus();
return false;
}}
if(ns4)_d.write("<scr"+"ipt language=JavaScript src=/menu/mmenuns4.js><\/scr"+"ipt>");
else _d.write("<scr"+"ipt language=JavaScript src=/menu/mmenudom.js><\/scr"+"ipt>");
</script>
function search()
{
if (document.searchform.elements["zoom_query"].value == "") {
alert("Please enter a word or phrase to search for.");
document.searchform.elements["zoom_query"].focus();
return false;
}}
if(ns4)_d.write("<scr"+"ipt language=JavaScript src=/menu/mmenuns4.js><\/scr"+"ipt>");
else _d.write("<scr"+"ipt language=JavaScript src=/menu/mmenudom.js><\/scr"+"ipt>");
</script>
(1) In the opening <script> tag, change JavaScript 1.3 to JavaScript. If you specify a version of JavaScript that the browser does not support, then it'll simply skip that block of code. And of course, if it skips that block of code then the menu code won't be loaded, and... no menu. I don't know what versions your browser supports, but if it's an old or quirky browser maybe it doesn't like 1.3
(2) Remove the definition for your search() function from the <script> block where the menu files are loaded. It shouldn't matter, but sometimes it does. Put that code in its own separate script block (and if the function requires js version 1.3, go ahead and specify the version there). Maybe like so:
Code:
<script type="text/javascript" Language="JavaScript">
if(ns4)_d.write("<scr"+"ipt language=JavaScript src=/menu/mmenuns4.js><\/scr"+"ipt>");
else _d.write("<scr"+"ipt language=JavaScript src=/menu/mmenudom.js><\/scr"+"ipt>");
</script>
<script type="text/javascript" Language="JavaScript 1.3">
function search()
{
if (document.searchform.elements["zoom_query"].value == "") {
alert("Please enter a word or phrase to search for.");
document.searchform.elements["zoom_query"].focus();
return false;
}
}
</script>
if(ns4)_d.write("<scr"+"ipt language=JavaScript src=/menu/mmenuns4.js><\/scr"+"ipt>");
else _d.write("<scr"+"ipt language=JavaScript src=/menu/mmenudom.js><\/scr"+"ipt>");
</script>
<script type="text/javascript" Language="JavaScript 1.3">
function search()
{
if (document.searchform.elements["zoom_query"].value == "") {
alert("Please enter a word or phrase to search for.");
document.searchform.elements["zoom_query"].focus();
return false;
}
}
</script>
Good luck,
Kevin
Poster: Maz
Dated: Friday October 1 2004 - 1:23:09 BST
Wow Kevin has all the goodies.
I thought of one other thing that would help is preloadimages.js
Maybe someone knows where its located?
maz
Poster: John
Dated: Friday October 1 2004 - 3:31:27 BST
kevin3442 wrote:
(1) In the opening <script> tag, change JavaScript 1.3 to JavaScript. If you specify a version of JavaScript that the browser does not support, then it'll simply skip that block of code. And of course, if it skips that block of code then the menu code won't be loaded, and... no menu. I don't know what versions your browser supports, but if it's an old or quirky browser maybe it doesn't like 1.3
According to his client, all the updates have been applied. That means the JS should be 1.4.2 along with the current Safari. However, I do agree with getting the 1.3 out of there, along with the search.
Poster: nbozic
Dated: Friday October 1 2004 - 13:29:54 BST
Thanks Kevin! I'll definitely try that, it kinda makes sense - it could actually fix the problem.
Also, I'm glad that you (John & Maz) couldn't see any problems with mac os x, which tells me that at least the problem is not "widespread".
Thanks,
NB