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.0Multiple Views with QueryStringsMultiple Views with QueryStrings
Previous
 
Next
New Post
8/6/2007 1:36 PM
 

 

So, is this down to personal preference?  Is there a best practice like NavigateURL() - or is that really designed for simple modules which have one view and one edit page?

I quite like the idea of defining these controls in the Module Definition as then it is an obvious place for administration.  Can you use NavigateURL in those circumstances? 

Pseudo code:

For creating an event:

NavigateURL("createevent")

For editing an event:

NavigateURL("editevent") + "&eventid=1"

This just seems cleaner than having to define the ascx files in the code behind.....

 

 
New Post
8/6/2007 2:18 PM
 

Maybe you can try this:

protected void lnkCreateEvent_Click(object sender, EventArgs e)
    {
        Response.Redirect(DotNetNuke.Common.Globals.NavigateURL(
            PortalSettings.ActiveTab.TabID,
            "","ControlType=createevent" ));

    }
    The NavigateUrl do support customer querystring, the problem is that you put it in the second parameter ,so it will be treated as the default "Ctl" parameter.

 


Over 20 + professional dnn modules for News Article, Store, Video Gallery, Photo Gallery, Ultra Flash Player,YouTube Video, Image Slide show, Skin Chameleon and much more from DnnModule.com
 
New Post
8/6/2007 6:18 PM
 

Perhentian wrote

 So, is this down to personal preference?  Is there a best practice like NavigateURL() - or is that really designed for simple modules which have one view and one edit page?

I quite like the idea of defining these controls in the Module Definition as then it is an obvious place for administration.  Can you use NavigateURL in those circumstances? 

Pseudo code:

For creating an event:

NavigateURL("createevent")

For editing an event:

NavigateURL("editevent") + "&eventid=1"

This just seems cleaner than having to define the ascx files in the code behind.....

 

NavigateULR is not restricted to 1 view and 1 edit. You can define any number of controls and pass them as parameters.  Those that do not have key values are the ones used as default for the view and edit screens respectively.


Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Multiple Views with QueryStringsMultiple Views with QueryStrings


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