Jump to:
| Project: | Signup |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Both for signup_status in the short term, and the proposed signup_fields module in the long term (#29568: Flexible number and type of fields), so long as signup.module itself is responsible for a global signup limit for each node, we're really going to need some way for submodules to hook into the total signup count for cases where a signup shouldn't affect the limit (#45419: using signup to track who can not attend, maybes, etc). If someone signs up to say "can't attend", that shouldn't count towards the limit and shouldn't show up in the UI in places where the total signups are printed. signup_status has a UI for this, but there's no good way for it to work without a change to signup.module.
I'm not positive what this hook should look like yet, but I wanted to open an issue as a place to have the discussion.
Comments
#1
I think that signup.module should invoke a hook - maybe hook_signup_alter(), that would allow other modules to alter the signup data. It would pass in the full data of the form submitted for the signup, which would allow a module like signup status to check if the set status is of a type that alters the signup count. Signup module itself would store whether or not a signup should contribute to the total signup count.
#2
This is now fixed by:
#581734: Improve the signup API: add hook_signup_data_alter(), hook_signup_create(), and hook_signup_update()
#581652: Add a {signup_log}.count_towards_limit column and adjust limit logic accordingly
#3
Automatically closed -- issue fixed for 2 weeks with no activity.