> [Seems like google has not published my previous post (also fixed the
> prefix). Sorry if this post appears twice.]
I am moderating the list for now, to get people to use the right
prefix in their message subjects. The idea is that app authors can
configure their mail filters so that they receive only those messages
relevant to them. Speaking of which, you should use "(tables)", rather
than "(django-tables)".
Also, sorry for the delay - I am not using django-pagination, and had
to investigate first. The problem is that {% autopaginate %} tries to
replace the variable passed in with a paginated version - in your case
this fails, since "table.rows" is not a "simple" variable: django-
pagination does not handle the attribute notation.
While you could potentially call this a bug, solving it is between
hard and impossible, since the attribute may be readonly. In fact,
table.rows **is** readonly. I suppose though that django-pagination
should probably provide an option to place the paginated version in a
new context variable.
For now, you can solve this be using a temporary variable yourself:
return render_to_response(template.html, {'table': table,
'rows': table.rows})
Template:
{% autopaginate rows %}
{% for row in rows %}
....
{% endfor %}
> from README:
> table.paginate(QuerySetPaginator, page=1, 10, padding=2)
> gives "non-keyword arg after keyword arg"
Oh. That's an error in the readme. It should of course be:
table.paginate(QuerySetPaginator, 10, page=1, padding=2)
I fixed it in bzr. Note however that this is completely different
approach than django-pagination. You probably want to use either of
the two, note both.
Michael