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.0Module Form ArchitectureModule Form Architecture
Previous
 
Next
New Post
2/10/2007 5:03 PM
 
Hi,

I have a Form in my module that has 15 criteria to choose from. When I submit this Form the results are displayed in a DataList on the same page. I have a Hyperlink within the DataList that shows the details of the search query on another page. I am passing the record Id in the querystring to populate the details. The problem I am facing is when I click the back button on the browser in the details page to go back to the Search form, I get a Page Expired page. I realize that this is by design as the previous page has posted data.

How could this be overcome, what suggestions would you give to design a page with these requirements?
Thanks
 
New Post
2/10/2007 6:24 PM
 

You may be too far into your current project to consider this, but using MultiView and View controls usually allows you do make DotNetNuke "act the way you want". By design DotNetNuke interprets requests for it's pages using a logic that allows it to do things like inject the proper skin and handle security. As developers we sometimes run into situations where it "wont act the way we would like it to".

Using the View controls allows you to put the criteria on one panel, Show the data list on another panel, have the click on the data list show details on another control that was invisible until you made a selection, and have a back button for the user to click (use the Wizard control if you have a lot of steps to keep track of).

If you come from the old classic asp days like me you're used to jumping from page to page. DotNetNuke doesn't really like that too much. Using View controls can usually solve all your problems. You can put a massive amount of functinality on the page and you actually end up with a lot less code.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
2/10/2007 8:04 PM
 
Michael,

Thanks for your detailed insight into the DNN architecture and how the pages work in this environment. I too have extensive ASP experience and have built applications in .Net with some page to page jump. I have not used Multiview too much but after you mentioned it I think that it would be a very viable option for my design. I might be too far in my design but I would like to code this module the way it should work seamlessly in the DNN environment. I will give it a shot. Thanks again.
 
New Post
2/10/2007 8:46 PM
 

Is there a reason you are jumping to another page to display the details? Is it because you want everything else off the page and you want more room?

If so I would use NavigateURL: How to make a link (VB &C#) . Some people don't like this because it causes DotNetNuke to use the "Admin panel" (all the other modules on the page disappear) when you navigate to another user control using this method. However, I use this a lot because I want all the other things to go away and for the user to concentrate on the page I am displaying to them. And for me the back button usually works in this case.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
2/10/2007 11:04 PM
 
Yes, that is partly the reason to jump to another page, I have tried the NavigateUrl and didn't like when everything else disappears. You are right, it does give more room but sort of takes away from the consistency of the site.

Jumping to another question, I tried to dynamically load one of my User Controls which inherits from PortalModuleBase into my page which has the search form as a test to use the View and Multiview. I was unable to access a public property on my User control.

ViewDetails.ascx has the following public property:
public int DetailsId
        {
            set {  this.detailsId = value; }
        }
 
In the Main page or module I load my User Control which loads and displays fine:
            UserControl ctrl = null;
            ctrl = (UserControl)LoadControl("ViewDetails.ascx");
             plhDetails.Controls.Add(ctrl);

I can not access this: ctrl.DetailsId
Any ideas on why? This works in a stand alone asp.net application.
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Form ArchitectureModule Form Architecture


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