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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0NavigateURL not working, EditUrl is.NavigateURL not working, EditUrl is.
Previous
 
Next
New Post
1/21/2009 2:36 PM
 

I've searched for this problem and I've found several posts of people having this exact same problem but I never see their issues resolved.

I have a module with two VIEW controls and I want to be able to switch between them.
 
I tried to use NavigateUrl from my default control but my module doesn’t show up on all on the page. If I use EditUrl from the default control I get my module but it shows the module container even though I turned it off for the module. The default control doesn’t show the container but the other VIEW control will.
 
 
So my questions are, what do I do about the NavigateURL issue? I’d like it to work so that I still get all other page modules when I switch controls. Also, when I use EditUrl, why does it show the container even though it is off in the module settings?
 
Any help you guys can give would be great. Thanks
 
Peter
 
New Post
1/21/2009 3:56 PM
 

Just add the ModuleId parameter to the query string and it should work. Something like:

NavigateUrl(TabId, "ViewWizard_Notification", "mid=" + ModuleId.ToString());

Container will always show up... It's part of the core so it will always appear with the admin defined container unless:

a) You rewrite the query string to specify a blank container (try clicking the print icon of any of the containers and check the query string generated to know what i mean).

b) You define a blank container specifically for the admin skin.

c) You use a multiview control to hide/show content. Check here: http://www.adefwebserver.com/DotNetNukeHELP/Misc/ModuleNavigationOptions.htm

Cheers, Al
 
New Post
1/21/2009 4:18 PM
 

After having answered this question a few different times, I decided to write up a blog post on the subject.

Hope it helps,

P.S. note that Al's solution of adding "mid" to NavigateURL is just going to get you the same results as using EditUrl.


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/21/2009 4:30 PM
 

Shall we make it a sticky then? The subject is pretty descriptive for this one.

Cheers.

 

 
New Post
1/21/2009 5:13 PM
 

Thanks Brian.  Your blog post makes sense and answers my questions.  I was curious how DNN knew which module to load the control for and now I know that it doesn't.  Why does the ControlKey parameter even exist in the NavigateURL then?  When could the ControlKey parameter in the NavigateURL ever work? 

Seems like there should at least be an enhancement to DNN to catch this case and put an error in the event log.  Had it been there I would have seen it right away, understood, and moved on.

Gonna spend some time to read the module navigation tutorial you linked to now.

Thanks again Brian.

Peter

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0NavigateURL not working, EditUrl is.NavigateURL not working, EditUrl is.


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