signup 6.x-1.0-rc3

I lied about the feature/API freeze for the DRUPAL-6--1 branch. ;) I think I was a little premature with that, and found some API and schema changes that were too good to leave out of the 6.x-1.* series. I also added some nice UI improvements and new features. I promise things will settle down for real once 6.x-1.0 is out, but there might be a 6.x-1.0-rc4 with a few more new features. Nothing too drastic, I hope. And, I won't be changing the signup API (hooks it invokes, etc) anymore, unless we run into things that would really simplify life for Signup status and friends. Sorry for the slightly bumpy ride, but I think you'll agree the results are worth it.

New features since version 6.x-1.0-rc2

• #349292 by dww: Completely reorganized the signup node tabs. All tabs added by this module now appear as sub-tabs under the "Signups" tab at node/N/signups. If the signup form is configured as a tab, it is the default task under 'Signups'. The list of current signups (for those with 'view all signups') is now at node/N/signups/list, and is the default task if the signup form is still on the node itself. The "signup-broadcast" tab has been moved to node/N/signups/broadcast. Finally, the admin form to add another user has been split off from the administrative tab (what was node/N/signups) and is now a separate tab at node/N/signups/add.
• #348277 by dww, scottrigby and stBorchert: Added a view field handler to provide links to any of the tabs under node/N/signups (#349292).
• #55168 by dww: Added a way to track attendance at node/N/signups/admin, including Views handlers to display, sort, and filter by attendance.
• #348559 by dww: Added a new "cancel signups" permission so that a role could be configured to view signups and record attendance, but not be able to destroy signup data by canceling other people's signups. There is no automatic upgrade that adds this new permission, so if you want to give any roles the ability to cancel other users' signups, you must visit admin/user/permissions and manually assign this new permission to the appropriate roles.
• #325237 by dww: Added support for a %cancel_signup_url email placeholder which points to a new signup/cancel/%/% page so that any users (even anonymous) with the 'cancel own signups' permission can now securely cancel their own signups.

Bugs fixed since version 6.x-1.0-rc2

• #347234 by dww: Fixed fatal SQL error at admin/content/signup when there are multiple node types using the same CCK date field.
• #343789 by KarenS: Fixed undefined value when adding nodes with feeds.
• #346810 by dww: Fixed invocation of hook_signup_cancel() so that the record in the {signup_log} table still exists when the hook runs.

API/Schema changes since version 6.x-1.0-rc2

• #341382 by Sid_M and dww: Added a serial "Signup ID" (sid) field as the primary key for the {signup_log} table.
• #347601 by dww: Changed the API for signup_cancel_signup() so that it either just takes the signup ID (sid) or a full object containing all the fields from the {signup_log} table.
• #347601 by dww: Changed the API for hook_signup_cancel() so that it is now invoked with a $signup object with the full information about the signup being canceled, and a fully loaded $node object. See the new signup.api.php file for full documentation on the hook.

Other changes since version 6.x-1.0-rc2

• #337614 Signup's optional Views integration now requires Views version 6.x-2.2 or later.

Known bugs

• #350872: Table, Column and Alias names in SQL queries should be quoted.
• #181272: can't translate labels on the signup form?
• #354944: Settings lost after previewing a node
• #350548: Signup closing when event node is edited