Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.As stBorchert pointed out over at http://drupal.org/node/137911#comment-317292 (comment #17), the views_handler_arg_signup_uid() function is adding an inappropriate WHERE clause to the SQL query. It's forcing the argument to filter on nodes where signups are still open. That should be handled via the existing signup status filter, instead of being built-in to the UID argument handler.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | signup_views_uid_handler_0.patch | 701 bytes | stborchert |
| #1 | signup_views_uid_handler.patch | 680 bytes | stborchert |
Comments
Comment #1
stborchertSimply removed the appropriate line.
Comment #2
dwwI think we should remove the {signup} table from the query, too, then... Doesn't seem necessary if we're not implicitly filtering on signup.status. We'd want to remove this line, too:
All of this requires a little more thoguht, investigation and testing, however. ;)
Comment #3
stborchertOk, I've removed both lines and tested if there any side effects. There aren't any :-)
The other code doesn't depend on table {signup} so there seems to be no problems and unused code.
Comment #4
dwwConfirmed, and committed to HEAD. My default "signup_current_signups" already had a filter for signups that were open, anyway, so this didn't even break http://drupal.org/node/137911. ;) Woo hoo. Thanks.
Comment #5
(not verified) commented