ajax - Webgrid: URL for Sorting and Filtering -


i have webgrid in partialview. parial view contains ajax form pass data webgrid. view looks like

using (ajax.begin("gain", "gaining", new ajaxoptions{updatetargetid="res"})) {  } <div id="res">   <div id="grid">      @{var grid = new webgrid(source: model.mylist, canpage: true, rowsperpage: 25, ajaxupdatecontainerid: "grid",                         cansort: true);     grid.pager(mode: webgridpagermodes.all));     @grid.gethtml(htmlattributes: new { id = "grid" },     columns: grid.columns(     grid.column(columnname: "num", header: "number"),         grid.column(columnname: "name", header: "full name", cansort: true)      ));    }    </div> </div>

the page displays wells sorting , moving next page not work. when try, grid dissapears. notice when hover on column header, when hover on header sorting links, url still localhost:xxxxx/#. when remove ajaxupdatecontainerid="res", url seems right: localhost:xxx?length=4?sort=name&sortdir=asc, wrong url given data obtained controller, gaining , method, gain

how can work please.or how can debug this? how sorting works?

edit

i confused use of ajaxupdatecontainerid. according this link, did not aid his/her sorting. if remove mine, whole partial view removed when click header link sort, or paging link. use of ajaxupdatecontainerid use then?


Comments

Post a Comment

Popular posts from this blog

Java sticky instances of class com.mysql.jdbc.Field aggregating -

i noticed (via jmap+jhat) app leaking storing many instances com.mysql.jdbc.field  class - double checked code make sure closing preparedstatements, find few missing didn't change outcome. - preparedstatement created , closed right away - several others created @ start , reused many times - using org.apache.tomcat.jdbc.pool.datasource connection pool what can cause type of behavior? are closing of preparedstatements / result sets using: preparedstatement stmt (possible assignment here); try { // work prepared statement resultset rs; try { while (rs.next()) ... // process results } { rs.close(); } } { stmt.close(); } so guarantee result sets closed when finished (regardless of exceptions) , statements closed (regardless of exceptions)? there other ways write that, idea same. if you're doing of properly, unless have many references it's taking inordinate amount of memory, it's ok , nothing needs done it.
Read more