Hi All,
We are using dnn:menu to display a list of menu controls like Home, Shop etc.

The problem we are having is when I click on the Home menu, it takes me to the Home.ascx page. but when i click it again it does nothing. I've to click for a second time to get that click event actually triggered.

has anyone come across a similar issue ?


is this a bug with dnn:menu control or is there a way about solving this problem..

Thanks,
Sridhar V

Do you have a Home.ascx page?

Which version of DotNetNuke are you using? Which web browser?

Hi jncraig,
First of all thanks for the prompt reply.

Yes, I do have a Home.ascx page.

We are using DNN Version 04.08.04
This happens to me in all the browsers. IE 7 and Firefox 3.0

Can you provide a link? Where did Home.ascx come from? Are you rewriting URLs?

Normally every DotNetNuke page is a version of Default.aspx.

Hi jncraig,

I believe the problem is not with the page navigation. Because on the second click its redirecting me perfectly. And Home.ascx is a webcontrol that I add to a DotNetNuke page.

What happens if you remove that custom control?

Joe,

you are asking me to remove the webcontrol (Home.ascx) from that page? is that what u mean.
If thats what you mean, I dont find any difference even after removing it.

This issue (double click on menu) occurs through out my site

Yes, that was my suggestion.  But, if removing doesn't change the behavior, we'll need to find something else.

You still haven't told me if you've created a special Home.ascx page outside of the DotNetNuke framework.  That's the way it seems based on your description.

No Joe. its within DNN Framework. I logged in as admin added a new page and then added the module(Home.ascx webcontrol). I hope its well within DNN Framework..

i'm a beginner with DNN, so Correct me if i m wrong.

OK. Home.ascx is a module or a skin object? I'm still not understanding the problem. What does it mean to say "using dnn"menu to display a list of menu controls"? What exactly is a menu control?

Joe.
here is how it is..
We've a skin "portalskin.ascx" which contains dnn solpart menu.

<dnn:menu cssnodeselectedroot="SelectedTabStyle" cssnodehoverroot="SelectedTabStyle" id="dnnMENU" runat="server" providername="DNNMenuNavigationProvider" usearrows="false">
lets say the menu contains Home, Products, Shop as the menu items. On all pages of our website we use portalskin.ascx as the skin so that the menu is available on all pages of the application. Ok ?

The problem is when I click on 'Home' it takes me to the Home page. Now from the Home page when I again click the 'home' menu item , it does nothing. I click the 'Home' menu item again for a second time, it reloads the page.

can you understand now ?

I understand, I hope.

I've never seen behaviour like that. Do you have any custom things on the page or in the skin?

Custom things? like ? I dint get you. Sorry

Is there anything on your home page or anything in your skin that isn't "standard" DotNetNuke.

You said that "And Home.ascx is a webcontrol that I add to a DotNetNuke page. " Where did this come from?

Yes. that's a module what we've written. We've created Home.ascx under DesktopModules and then added that to a DNN Page.

I have a feeling that might be interfering with the module navigation. 

If you completely remove any custom modules and also switch to a DotNetNuke skin, does the navigation work correctly?  That's what I'm trying to figure out.

If the navigation works with no custom modules or a custom skin, then start adding them back one at a time.  See which addition breaks the navigation.

Oh, and I'm still possibly confused whether it is the navigation that is broken, or whether it is something in your custom code that is broken.

Will change back to DNN Skin and check if its workin fine. if thats the case , there is some problem with the skin file.
if else ll try removing the modules one by one and check.

Thanks Joe. Will reply to this thread once i m done.

Thanks a lot

That's my fundamental approach to debugging.  First get a version that works.  Then, add stuff until it breaks. 

If you can then remove what you added and it returns to working, you've got a good place to start digging in.