Help - Search - Members - Calendar
Full Version: "cFrame is undefined error"
xFX JumpStart Public Forums > DHTML Menu Builder > Frames Implementation > Using HotSpots
chrisarmstrong
Hi Xavier,

I have read a bunch of posts on problems with 2 menus on the same page so I followed your advice and built the 2 menus into one project using hotspots.  The problem I get is that if you rollover the images I get a "cFrame is undefined" error.

Here is the link.  I am using Ver 3.6 rc1, don't know if that is the problem.

http://www.patentpendingideas.com/treetopf...ibrary/menu.htm

I actually built both of these as separate menus, and they both worked fine on there own, but I have to center them on the page so I switched it to Hotspots.

I was planning on using these menus as a library item for all the pages, but should I switch to a frame layout?

Thanks,
Chris
DMB file attached aswell
xfx
Here's the problem:

The loader code on your page is looking for a file called menu.js but the .js files on your web site are actually called iemenu.js and nsmenu.js

Why?
Because you installed the loader code into your page while the "Code Optimization" setting was in "DEBUG" mode. But you then switched it to "FINAL" and compiled your project.

While in DEBUG mode DMB creates just one file: menu.js but in FINAL mode DMB creates two files: iemenu and nsmenu.

So, whenever you switch the "Code Optimization" mode you must update the loader code on all the pages that require it and upload everything back to the server.

This situation is known as “out-of-sync”: your .js files are out-of-sync with the loader code.


NOTE: DHTML Menu Builder 3.6’s main feature is its ability to create two or more toolbars within the same project. So, if you wish, you can create the toolbars right into DMB and not use hotspots.
jruiseco
QUOTE (xfx @ Jul 23 2002, 05:08 AM) *
Here's the problem:

The loader code on your page is looking for a file called menu.js but the .js files on your web site are actually called iemenu.js and nsmenu.js

Why?
Because you installed the loader code into your page while the "Code Optimization" setting was in "DEBUG" mode. But you then switched it to "FINAL" and compiled your project.

While in DEBUG mode DMB creates just one file: menu.js but in FINAL mode DMB creates two files: iemenu and nsmenu.

So, whenever you switch the "Code Optimization" mode you must update the loader code on all the pages that require it and upload everything back to the server.

This situation is known as “out-of-sync”: your .js files are out-of-sync with the loader code.
NOTE: DHTML Menu Builder 3.6’s main feature is its ability to create two or more toolbars within the same project. So, if you wish, you can create the toolbars right into DMB and not use hotspots.


Can you provide detailed and specific steps to overcoming this problem? I am experiencing this and cannot get it fixed to save myself.

Josen
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2012 Invision Power Services, Inc.