Have updated issue 454 which was previously closed. This works with ajax=True (seems to work with multiple tables too though I have not fully tested) if you have a separate controller for each table. However:
1) It does not work with ajax=False and ajax_trap=True. In this case clicking a paginate button opens a new page. 2) If you have a more complex controller then paginate does not work as it does not pass the table name. e.g. if my controller does <<return grid(db[request.args(0)])>> then paginate buttons will not work as the table name is not passed as a parameter. On Oct 11, 9:30 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > If an ajax grid does work please open an issue on google code so I can > check it and we can fix it. I cannot reproduce your problem otherwise. > > On Oct 11, 1:12 pm, apple <simo...@gmail.com> wrote: > > > > > > > > > Surely there must be a solution to this? It does not seem logical to > > have a component that is arbitrarily restricted to one per page? > > > iframe is not a good solution. And I don't think LOAD with ajax works > > with multiple grids and pagination - certainly it does not work in my > > application even after the recent fix in trunk. I have got multiple > > grids to work with LOAD and no ajax, including the add/view/edit but > > not pagination. > > > Surely there are many possible solutions to this without compromising > > the URL benefits you mention. For example you could include a "gridid" > > in request.args or request.vars; maybe also save the grid parameters > > in session. > > > On Oct 11, 3:44 pm, Anthony <abasta...@gmail.com> wrote: > > > > On Tuesday, October 11, 2011 9:49:51 AM UTC-4, stefaan wrote: > > > > > (workaround: e.g. use iframes, or design a better UI that doesn't need > > > > two grids in one view ;) > > > > Using ajax components might be better/easier than iframes.
