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...

---

Thanks,
Rodney
Smart-Thinker - Home of SmartSocial - the 100% Free DotNetNuke Social Networking Product Suite
Do use DNN a lot? Try the DotNetNuke Toolbar to save you time!
PokerDIY - Example Implementation of DNN Social Network

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

---

Erik Hinds
Risdall Marketing Group
#1 Web Design Agency in the World

www.risdall.com | www.risdall.net | erik AT risdall DOT-COM

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.