signup 6.x-1.0-rc2

Bug fixes since version 6.x-1.0-rc1

• #336255 by KarenS and dww: Fixed numerous bugs in usage of DateAPI that were breaking all time-based signup functionality for datestamp fields and causing problems for certain configurations of date or datetime fields depending on the timezone handling. Using 6.x-2.0-rc5 of DateAPI and the CCK Date field, the one configuration that doesn't fully work is a datestamp field that has no timezone handling at all. With that configuration, you must use the latest Date code from the DRUPAL-6--2 branch (check the top of your copy of date/date.module and make sure the revision is at least "1.61.2.4.2.34" (2008-11-28) or newer).
• #338850 by dww: Fixed critical SQL bug ("Not unique table/alias: 'e'") on the signup administration page (admin/content/signup) for sites that have more than one event.module node type that is signup-enabled.
• #335190 by bkat and dww: Fixed bug where if you had a node enabled for signups and edited it to disable signups, the node would remain signup enabled. The bug was introduced in Signup version 5.x-2.6 by #328822.
• #336442 by dww: Fixed bugs with the views filters "Signup: Enabled/Disabled" and "Signup: Confirmation: Enabled/Disabled".
• #336461 by dww: The "Signup: Reminder: Enabled/Disabled" views filter was broken since it was using the wrong filter handler.
• #336450 by dww: Fixed the UI for signup's Views filters.
• #336610 by dww: Fixed bug introduced in #329668 where node types that have an underscore in their name had broken links in the warning messages about CCK date fields being misconfigured. Those warnings also didn't appear at all in some cases. The bug was caused by core's bizarre handling of node_type vs. node-type in URLs.
• #340377 by dww: Fixed bug where the default value in the database for how many days in advance to send reminder emails did not match what the rest of the code was written to expect. Reminders would not be sent until the admin/settings/signup page was saved.

Other changes since version 6.x-1.0-rc1

• #335563 by dww: Added support to control the relative ordering of the signup information embedded on nodes. If the content.module (CCK) is enabled, "Signup information" is now exposed to the field management page (where there is a drag-and-drop interface to reorder everything) at admin/content/node-type/[node-type-name]/fields. If CCK is disabled, there is a variable to manually control the weight. The variable is called "signup_info_node_weight_[node_type]" and can be defined in the $conf array in settings.php.
• #336129 by dww: Moved the signup node type settings out of the "Workflow" fieldset into a separate "Signup settings" fieldset.
• #341331 by dww: Improved database performance during cron runs by using INNER JOIN instead of LEFT JOIN for finding nodes of a given type that need to be auto-closed and/or have reminder emails sent.

Known bugs

• #347234: Not unique table/alias SQL error on admin/content/signup if you use the same CCK date field for multiple node types (Note: everything else works fine -- it's just the site-wide signup administration page that throws the error).
• #343789: Undefined value when adding nodes with feeds