Pager is not visible - PRO

[dbadmin]

Oh, I got it now! It shows the pager now, thank you.

So would this be the right way to pass current page to the service VIA $POST?

                          getUrl: function (ui)
              {
                 var pageModel = ui.pageModel;
                 var filters = { "name" : $("#txName").val(),
                             "curPage": pageModel.curPage,
                             "recPerPage": pageModel.rPP,
                                 };
                   return {
                    url: "../services/Search.php",
                     data: { dataBuffer: filters }
                };
            },

I also have a question in regards of totalRecords. I prefer not to calculate total and leave it blank, but then pager misbehaves. Is there a way to handle this situation?

[dbadmin]

Hi,

So could you tell me if this is the right way? I often get current page = 0 and it doesn't seem to be correct.
Also when I change the filtering field (Name) and search again, CurrentPage value is retrieved from a previous search, so it creates a problem when previous search had page 5, and a user was on page 5, but new search only has 3 pages -- a user gets an empty resultset.

Thanks!

[paramvir]

That's the right way to send parameters to the server. However the end result in the grid i.e., remote paging and remote filtering is little bit dependent upon on your javascript and more dependent upon how you handle the parameters on the server side. If you write incorrect PHP code, you would get incorrect result in the grid.

The benefit of using paramquery filter method and following the demos is that it takes care of

sending filter parameters on its own
protects against SQL injection attacks.
you can use the already written filterHelper method in PHP.

http://paramquery.com/pro/demos/filter_header