Using the core DNN Pager control - General Discussion

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

Home All Forums

Home

Our Community

General Discuss...

Using the core DNN Pager control

1/3/2007 9:54 AM

Rodney Joyce

www.pokerdiy.com
Joined: 4/28/2004

Posts: 2796

Using the core DNN Pager control Modified By Rodney Joyce on 1/3/2007 9:56:03 AM

Hi,

I'm having a look at the core DNN Pager control and was wondering why the choice was made to use the Querystring to post values instead of a normal postback event. For example, if you go to the next page it bungs the CurrentPage and Filter into the querystring and effectively requests the page again. This means that anything on the page is reset - you can see this in action by going to the core User search and typing a value and changing the DDL to a property. A list of values is returned, but if you page then it loses the value of the DDL and filter (which is a bug as it means you can't page users).

I was about to use this but then I had to start hacking anything that I wanted to persist into the Querystring and that look ugly and becomes unmanageble. I don't understand why the control does not just postback with a Next or Last event which could be used to increment the PageNumber etc without having to hack around with the URL?

Any advice would be appreciated...

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

1/3/2007 12:53 PM

William Severance

www.wesnetdesigns.com
Joined: 2/18/2005

Posts: 3253

Re: Using the core DNN Pager control

Rodney,

I was wondering the same and initially wrote my own pager control that did not user the querystring to post paging values but rather kept them in viewstate and posted back with a page changed custom event. I later came to the conclusion that the reason the DNN pager control uses the querystring is to make it possible for users to bookmark a particular page of data or to copy the url with paging values from the browser address bar and paste it elsewhere. I've since switched over to using the DNN pager. As you've seen in the problem you mentioned with paging the admin users table, it is essential to pass ALL of your own parameters (such as from a filter) back into the DNN pager using its QuerystringParams property.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

1/3/2007 2:14 PM

Erik Hinds

Joined: 8/20/2004

Posts: 1053

Re: Using the core DNN Pager control

I have also noticed that when you use the dnn paging control, you cannot have multiple girds on the same page.

1/4/2007 4:46 AM

Rodney Joyce

www.pokerdiy.com
Joined: 4/28/2004

Posts: 2796

Re: Using the core DNN Pager control

Thanks for your thoughts - it just seems really clumsy as if you have ANY control on a page that uses it you have to manually do query hacking to maintain their state.

I am working on an Advanced Search and I'm going to have to pass in the value and DDL value of every control so that the selected values are persisted when it requests the page again! Seems to be counter-productive to the ASP.NET page life-cycle somewhat.

There are a few more bugs in the core search then - the DDL does not keep it's value and the search string is not written back to the search textbox when it is requested again.

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

1/5/2007 1:00 PM

Brian Price

Joined: 10/5/2003

Posts: 85

Re: Using the core DNN Pager control

I recently ran into the same limitation. Now I’m debating whether to write my own adaptation, enable the DataGrid’s paging UI or try to work with the DNN page control. The paging control is a template control. It would be nice if it supported custom templates for page indexes, first and last buttons. Then we could use the control and bind whatever type of control we want to the page index, i.e. a LinkButton.

In the past I ran into a similar problem with the DNN Wizard control. I think the DNN controls are designed to work in a specific context. When I try to use the controls outside of that context I run into problems.

Qualtiy DotNetNuke modules and custom development; we've been serving the DNN community for over 2 years and have hundreds of satisfied customers. Let us serve you today.

Page 1 of 2

Home

Our Community

General Discuss...

Using the core DNN Pager control

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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

DNN Corp. (DotNetNuke)