djvk87
03-01-2011, 01:25 AM
Hi all,
quite a while ago I posted on the DD forums about a problem I've had with 2 scripts (both from here) conflicting with each other. The conflict is between Drill Down Menu (v1.6) (http://www.dynamicdrive.com/dynamicindex1/drilldownmenu.htm) and Dynamic Ajax Content (http://www.dynamicdrive.com/dynamicindex17/ajaxcontent.htm).
I use the Drill Down Menu system to load dynamic ajax pages.
This all works fine on Firefox 3.6 but when I try another browser the Ajax pages fail to load and in Internet Explorer 8 an error appears in the bottom status bar saying "'document.getElementById(...)' is null or not an object".
When I last posted about this I was told that IE cannot handle global variables with the same name as an DOM element ID, especially if that variable is actually pointing at that DOM node and that I should try changing the id to something else and maybe it will work. But I never did figure it out as I'm quite a noob at javascript.
I originally thought the problem only happened in Internet Explorer but I've found it also happens in Google Chrome and Firefox 4.0 beta versions.
I am desperate to get this working and I'm prepared to pay for a working solution. The webpage is http://woodenboatshop.com.au/yanmar/spareparts.php
quite a while ago I posted on the DD forums about a problem I've had with 2 scripts (both from here) conflicting with each other. The conflict is between Drill Down Menu (v1.6) (http://www.dynamicdrive.com/dynamicindex1/drilldownmenu.htm) and Dynamic Ajax Content (http://www.dynamicdrive.com/dynamicindex17/ajaxcontent.htm).
I use the Drill Down Menu system to load dynamic ajax pages.
This all works fine on Firefox 3.6 but when I try another browser the Ajax pages fail to load and in Internet Explorer 8 an error appears in the bottom status bar saying "'document.getElementById(...)' is null or not an object".
When I last posted about this I was told that IE cannot handle global variables with the same name as an DOM element ID, especially if that variable is actually pointing at that DOM node and that I should try changing the id to something else and maybe it will work. But I never did figure it out as I'm quite a noob at javascript.
I originally thought the problem only happened in Internet Explorer but I've found it also happens in Google Chrome and Firefox 4.0 beta versions.
I am desperate to get this working and I'm prepared to pay for a working solution. The webpage is http://woodenboatshop.com.au/yanmar/spareparts.php