Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

Affordable ASP.NET Hosting Service
  Ads  
 


  Sponsors  

Meet Our Sponsors

SmarterTools
Verndale
The Official Microsoft ASP.NET Website
Portal Webhosting - Hosting For Developers
Red-Gate Software
MaximumASP
 


DotNetNuke Forums
 
  Forum  DotNetNuke® Pro...  Blog Module [Le...  Blog and housemenu
Previous Previous
 
Next Next
New Post 5/5/2008 8:21 AM
User is offline Sian Okeeffe
37 posts
10th Ranked


Blog and housemenu 

Hi

We are using DNNv 4.8.2 with the housemenu skin object.

Our problem is as follows :

  1. We have 2 differet menu displays for top level and second level menus.
  2. We created a top level menu itm called COMMUNITY. This displays properly according to the CSS.
  3. We added a page called blog, and set COMMUNITY to be the parent page. The page displays correctly as a second level menu itm according to the CSS.
  4. As soon as we add the blog module to this page, the second level menu itm all of a sudden changes and displays as a top level menu - even though its a second level menu ?

Has anyone had this problem at all ? Can anyone suggest a fix ?

We are experiencing the same issue with the forum module ...

Thanks in advance :)
 
New Post 5/5/2008 10:35 AM
User is offline Dario Rossa
366 posts
www.dariorossa.it
8th Ranked




Re: Blog and housemenu 

Hi Sian,

after adding the Blog module to the child page, do the page's settings change? I mean: in page settings do you still have a parent page or did the page become a top level page? This will lead to two differet scenarios:

  1. The page has become a top level page. This was caused by adding the modules, and is very strange, I never heard about something like this. In any case this could be solved changing back the settings and setting a parent page as desired.
  2. The page still have a parent page. This means that the problem resides in the housemenu skin object, and the way it handles newly added modules, I guess.

Let us know.

Best regards
Dario Rossa

Dario RossaDario Rossa
Personal WebSite: http://www.dariorossa.it
DotNetNuke: http://dotnetnuke.dariorossa.it
 
 Page 1 of 1
Previous Previous
 
Next Next
  Forum  DotNetNuke® Pro...  Blog Module [Le...  Blog and housemenu
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
 


Code 5 Systems, LLC.
The DNN Missing Link: A Form Module. Form Master 1.6 is an intuitive Form Creation Module at a great price. Quality Custom Module development, and DNN consulting services.
www.code5systems.com 		SSL Enabled and Amazingly FAST...
SSL enable your DNN web site with SSLRedirect, compress your DNN web site HTTP data flow by up to 75%-90% with HttpCompressionAgent, and monitor your DNN web site's performance with WebKeepAlive...
www.sanibellogic.com 		Ultra Media Gallery & Video Gallery
The most popular photo gallery and video gallery module. with Flash interface.
www.bizmodules.net

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP