I'm enjoying some success and experiencing some frustration with the
JSCookMenu v.1.1.2.  I have it working great in one section of my site,
but having some problems in another.

In the problem area, I had created a CSS/JavaScript menu with command
links, but the JavaScript IE fix to trigger mouseover actions isn't 100%
reliable.  Therefore, I want to replace it with the JSCookMenu, but two
problems are preventing me from doing so.

1. When the site first loads, the menu is not rendered and I get a
javascript error stating that CM_Panel is not defined.

2. When a user logs in, the menu does loads fine and the javascript
error dissapears.  However, the menu entries do not work.  The page
submits but reloads the same view.  The menu is part of a header file
that also includes a 'login' section which may be part of the problem.
Each unsecured page has the username and password fields in the header,
waiting for the user to log in.  When the menu is clicked, the
validation on these fields is NOT triggered, but the navigation is not
engaged.

For those of you using this component, what are some of the pitfalls to
avoid?  Do these issues sound familiar?

Thank you

  • JSCookMenu James Reynolds

Reply via email to