Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIDNNMenu - Differences in rendering/click action DNN 4.09.02 vs DNN 5.0.01DNNMenu - Differences in rendering/click action DNN 4.09.02 vs DNN 5.0.01
Previous
 
Next
New Post
3/13/2009 12:32 AM
 

For the new version of the DNN Gallery module, I replaced its use of the SolPartMenu with DNNMenu both for the main gallery menu and the thumbnail context menus. In both cases, the menu control and its child nodes are dynamically created in code. While this works well in DNN 4.09.02, we are encountering differences in both rendering (not apparent visually but vastly different in the html source) and the handling of a click over a menu node's text when the gallery module is installed on a DNN 5.00.01 site. On DNN 5.00.01, clicking a menu node icon properly results in navigation to the url specified in the node's NavigateUrl property. However, clicking the menu node's text, results in a postback but no navigation.

I have set up the latest Gallery build on both a DNN 4.09.02 and a DNN 5.00.01 site to demonstrate what is happening. Hover over a gallery thumbnail and try clicking on the node's text. On the 5.00.01 site, a postback occurs but there is no navigation to the selected control. Click on the node's icon and all is well.

The test installs are located at:

DNN 4.09.02 site: http://www.wesnetdesigns.com/DNNGalleryTest/tabid/127/Default.aspx
DNN 5.00.01 site: http://www.men-on-fire.org/Gallery/tabid/72/Default.aspx

The gallery module install package is built with DotNetNuke.dll (v 4.9.1.42), DotNetNuke.WebControls.dll (v 1.5.3.20116) and DotNetNuke.WebUtility.dll (v 3.2.00) with SpecificVersion set to false in both references. If the gallery module is re-built (with no changes in code)  against DotNetNuke.dll (v 5.0.1.189), DotNetNuke.WebControls.dll (v 2.0.337.0) and DotNetNuke.WebUtility.dll (v 4.0.337.0), and installed on a DNN 5.00.01 site, clicking over the menu node text or the icon work properly.

Jon, could you please take a look at this and offer suggestions as to what might be happening here? Let me know if you would like either a code snippet of how the menus/nodes are being constructed or the latest gallery source package. Thanks!


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
3/13/2009 2:46 PM
 

Looks like you are putting HTML into your menu text entries for the purpose of causing a nowrap in your style.  This is causing a problem since you are assigning an id to the span.  If you do not specify an ID then the problem should resolve itself.  As far as what the difference is between dnn versions, dnn5 uses the new menu where I made some major changes (optimizations).  The code no longer needs to take the event.target and loop up the chain until it finds an element with an ID.

Along those lines, you should be happy to know that you can use css to handle your nowrap configuration for the new menu.

 


 
New Post
3/15/2009 1:41 PM
 

Thanks, Jon. Your analysis was right on. The span was to be placed around the menu node text ONLY in DNN 4.9.x to prevent text wrap which I could not seem to stop via any of the men's css classes. The span was not supposed to have been added for DNN v 5 in which the text was not wrapping. Unfortunately, my DNN version test was failing in DNN 5.00.01 resulting in the span being applied in that version as well. Correcting the version check solved the problem. I don't know how I missed that one . . .

Regarding the need for wrapping the menu node text with this span to prevent word wrap in DNN v 4.9.x, is that the right approach or is there a better way to block the wrapping via adding white-space: nowrap to one of the menu's css classes?


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
3/16/2009 9:04 AM
 

You should be able to accomplish the same thing with the following class declaration

.MediaMenu_MenuItem td span {white-space: nowrap;}

 

 


 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsClientAPIClientAPIDNNMenu - Differences in rendering/click action DNN 4.09.02 vs DNN 5.0.01DNNMenu - Differences in rendering/click action DNN 4.09.02 vs DNN 5.0.01


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out