it says Microsoft Inernet Explorer Cannot open the Internet site
http://dnn.wsysa.com/Default.aspx?tabid=57

Operation Aborted

[Click OK]



Is this a common issue with 3.0.10? It's running on a production server where the resource usage is rather low. It takes about 20-40 page clicks to find the error but it does pop up.

The strange thing is that the page loads ok.


I'm considering moving our public internet site to DNN in the next few months, however I think I'm going to wait for the Final 3.0 build.

It doesn't appear that many people have read this thread.

However, I was able to duplicate this bug on the Main DotNetNuke (www.dotnetnuke.com)Site, within 3 clicks.

It however didn't display the page, it just died.

If it helps, I click the links, while not waiting for the page to load again. I was able to duplicate the problem from 2 different locations, both running IE6 Windows XP.

Reading the past posts this seems common.

I suppose my question is how can I avoid the propblem from cropping up, is there a work-around?


One of the posts mentioned an alpha setting, what is that?

Are you sure this is not client related? normally an operation aborted error has something to do with the client .... What is the exact error you are getting? Did you test this on other machines? Did you test it on a different network/network connection?

erik

I, too, have been experincing this issue, and have been able to recreate it on cue.

To recreate it, I have a portal site with a full width, horizontal menu. When I click on one of the page links in the horizontal menu (for instance, "Home"), and then QUICKLY move my mouse over the main menu's "Admin" link while the browser is "thinking", my browser window will flash, and then I get the following error dialog:

---------------------------
Microsoft Internet Explorer
---------------------------
Internet Explorer cannot open the Internet site http://www.thejordanfamily.org/mjj/Guestbook/tabid/78/Default.aspx.

Operation aborted


---------------------------
OK
---------------------------

mark,

i tried to reproduce what your error, by visiting your site, but it i get no error .... this seems like a client error. Do you get any javascript error, do you have javascript debugging enabled? and friendly error messages disabled? ...

cheers,

erik

That's because you don't have access to any menu items that have multiple submenu items (I was using the "Admin" menu item when logged in under a superuser account).

I just added three sub-pages to the Guestbook item on the menu... 001, 002, and 002.

Now, to recreate this issue, goto http://www.thejordanfamily.org/mjj, click on the "Resume" menu item, and IMMEDIATELYand QUICKLY after clicking it, move the mouse to reside over the "Guestbook" menu item... you need to be really quick to move the mouse after clicking, before the new/requested page actually renders.

I have recreated this on several machines.... all were running Windows XP Pro with SP2 and the latest version of IE.

By the way, I am sure that this IS client related... I'm certain that it has to do with the client script that is used for the menu dropdowns. This may no be exhibited in non-IE browsers... I've only experienced it in the IE browser with the horzontal menu.

view post 641014.

This is also logged in the issue tracker support.dotnetnuke.com (though it is down right now).

The debate I have with making the delaysubmenuload the default is the performance penalty that it will incur weight against the few occasions where the operation aborted error occurs.

Note: You don't have to change the spmenu.js file to fix this like the listed post above indicates. You can now change your skin object (DelaySubmenuLoad="1").

Thank you!

where do I add DelaySubmenuLoad="1" in at?

In the skin (htm or ascx file). in the <dnn:MENU element or dnn:SOLPARTMENU depending on how you have it defined.

in your skin file. If you use HTML skins then add it as a property of the SOLPARTMENU token in the skin's XML filelike this

<Objects>


  ....


  <Object>


    <Token>SOLPARTMENU</Token>


    <Settings>


      ....


      <color=blue><Setting>DelaySubmenuLoad</Setting>


      <Value>1</Value></color>


      ....


    </Settings>


  </Object>


  ...


</Objects>

If you use ASCX skins then it is as Jon described it above.

I am producing the same problem discussed here, but - even with the appropriate changes for the delay - the error still occurs. Any other ideas? I know this bug is a documented bug in IE - and can be corrected by not placing the code that generates the appendChild javascript call into a TD, but there must be some better way around this.

Yeah, the problem still exists for me also.
The solution is don't use Heigharchial Menus, haha.  Then only an admin will run into the problem when he hovers over the admin menu.  Hopefully it is resolved in a future release, it's been around even in DNN 2.  Maybe The CSS Only Menu will not suffer from this instability. 

Don't take my post wrong, I like the solpart menu and commend it's designer for the flexibility and configuarbility(Is that a word). But for the webmaster of a large public site, it is not acceptable to put a product with these issues into production.

I'd also like to vent about the Remeber Me Feature of the login control, but I'll save that for another thread.