micki
Nuker Posts:14
|
09/02/2009 12:29 PM |
|
I have looked and may have missed it, but I am looking for a simple drop down menu that can be added to certain sections within a site, separate from the main navigation. Nice and simple. Does anyone know if there is there anything available? Would prefer not taking the time to figure out how to create modules I did find one, Select A Link Menu Navigation by netsignature, but when I go to test it on their site I get a server error on a few links and that scares me |
|
|
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
|
micki
Nuker Posts:14
|
09/03/2009 11:47 AM |
|
Thanks for the info and I am a little confused. For the main menu of the site, I am using the house of nuke. I am wanting to put a drop down menu, as a module, in the body of the page, say above the content on all pages of a particular section in the site. For example... Main link is Stories with lead ins to other stories, then have the drop down menu have links to the full stories in that section. My client does not like the way the main menu (house of nuke) automatically lists the sub-sections below the main links in the actual nav menu. I personally think that it is fine. I am trying to avoid redoing the whole site navigation and thought a simple drop down might resolve this. Does this make any sense? |
|
|
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
|
micki
Nuker Posts:14
|
09/11/2009 9:30 PM |
|
After spending time with this simple menu and building a skin to use it, it does not work. 2 of us have attempted and on further research there is another person having the same issues. I cannot find any help elsewhere, even on the Snapsis forum. Does anyone have any other suggestions for a simple dropdown menu that can be put on a parent page to allow child pages to be listed?
Any help is greatly appreciated! Aloha
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
09/11/2009 9:43 PM |
|
Which version of DotNetNuke are you using? |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
micki
Nuker Posts:14
|
09/12/2009 12:06 AM |
|
4.9.3
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
|
micki
Nuker Posts:14
|
09/12/2009 1:05 PM |
|
So far, If added to a page, it can only be seen if logged in as host, once logged out it disappears. Does not appear if logged in as admin either.\
thanks!
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
09/12/2009 10:13 PM |
|
Do you add to a page, or add to a skin? Is there documentation available? Where? |
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
micki
Nuker Posts:14
|
09/13/2009 12:41 AM |
|
it was added to a skin. i am sorry, don't understand what you are asking concerning documentation. Instructions included and followed:
Installation Procedure
1. Make a backup of your DotNetNuke folder (this is optional but good practice). 2. Unzip the Snapsis.DNN.NavList_1.0.0.zip download package to a directory of your choice. (you might have already done this to read this file) 3. Login to your portal as Host and install the Snapsis.DNN.NavList_1.0.0_PA_Install.zip as a custom module (Skin Object).
To use the SkinObject in your .ascx skin, just place the following code at the top to register it: <%@ Register TagPrefix="simpleNav" Namespace="Snapsis.DNN.Skins" Assembly="Snapsis.DNN.NavList" %>
Then just place the following code in your skin: <simpleNav:NavList id="navList" Level="0-3" IncludeTabs="*" ExcludeTabs="" runat="server" />
thanks for responding!
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
09/13/2009 6:16 PM |
|
I was actually wondering if there is documentation from the skin object. How do you know how to configure it?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
micki
Nuker Posts:14
|
09/14/2009 5:35 PM |
|
I took an existing skin and added as per documentation of skin object. |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
09/14/2009 7:26 PM |
|
I'm afraid that I'm coming up short here.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
micki
Nuker Posts:14
|
09/14/2009 11:31 PM |
|
For your info. Not sure whether the first guy ever figured it out or gave up or had a different communication that resolved the issue. Second huy has not had a response... http://www.snapsis.com/Support/tabi...ators.aspx I do not understand what you mean by coming up short... |
|
|
|
|
Joseph Craig DNN MVP Posts:11667
|
09/15/2009 7:48 AM |
|
Coming up short with a good answer for you is what I meant.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
|
micki
Nuker Posts:14
|
09/17/2009 11:59 AM |
|
okay, just for clarification, as this whole thing is for the simple drop down menu (free) ... the code given to insert into skin is this... (spaces added). < simpleNav:NavList id="navList" Level="0-3" IncludeTabs="*" ExcludeTabs="" runat="server" / > i appreciate the help! |
|
|
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
|
micki
Nuker Posts:14
|
09/17/2009 1:46 PM |
|
nope, did nothing, but thanks for trying!!! but since your here , i am using the housemenu for the main nav. my client does not like the way the child pages of a parent page shows up across the entire site. he only wants the child pages to show up in the section that they relate to. can this be done with this menu? i am thinking that i will have to create skins for any sections that this would apply. would it be easy for my client to update? and will any new pages added to the site show up on all menus? hummm, did the above make sense? thanks |
|
|
|
|
Lee Sykes DNN Creative Staff
Nuke Master VI Posts:4945
|
|