(Not sure if it's a bug, problem in the design or just a feature request - and I don't even know if its better places in the forms-api-section).

Using a form for submitting data to a pager_query works fine. But when using the pager-specific features (sorting, scrolling through the data etc) it doesn't work anymore.

The pager_query-functions are submitted by GET-statements. But forms primally works with the POST-method. The good thing is, that pager_query also submits the form-specific data like form_build_id or form_token (/site?page=1&formvalue=XXX&op=Action&form_build_id=form-05a475f6160efd619ad635130e4744f5&form_token=6dbac0e894dd93e2fcd9f8b1012dfd97&form_id=form).

With those form-specific data I made an (IMHO dirty) hack to rebuild the form. But I'm not very happy with it. There are good reasons, why pager_query works with GET and forms api with POST, but here it collides.

Comments

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.