Releases for Signup

Bugs fixed since version 6.x-1.0-rc4

• #533970 by dww: Fixed bug that caused the "signups" tab on nodes to generate an "Access denied" message unless the signup attendee list was configured to appear as a tab (introduced in RC4 via #529478).
• #534948 by dww: Fixed bugs where signup_confirm_email.module breaks signup_status.module due to the unorthodox way it was trying to hijack the signup form for the confirmation. Now, confirmation is handled via a checkbox (which is only shown if needed via JavaScript) instead of trying to redirect to a separate confirmation form.
• #536094 by dww: Fixed a UI bug when editing existing signups. If there was a form validation error (e.g. a required field was left blank), the form now reloads already in "edit" mode with all the fields enabled and the submit button already converted to "Save."
• #544882 by dereine: Fixed a few places that called node_load() so that they can now make use of the node caching feature.

New features since version 6.x-1.0-rc4

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

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.

This is the first official release candidate of the port to the Drupal 6 API of the Signup module. It contains all of the features and bug fixes from the Drupal 5 version up to and including version 5.x-2.6. Assuming no bugs are found, this will be released as the 6.x-1.0 version in the near future.

Changes since 5.x-2.6

• #222217 by dww, deadwood.module and coder.module: Initial port to D6. Related issues: #330838, #330840, #332968, and #333264.
• #330820 by dww and duellj: Ported all views support to the views2 API. This changes how the 'View to embed for the signup user list' setting works, so any sites that are using a custom view for this will have to revisit the signup settings page and select a new value under the advanced settings fieldset. signup_update_6000() removes the deprecated variables from the database.
• #330821 by dww: Fixed problems with the D6 CCK Date field support.
• #330824 by dww: Ported the Panels integration to the D6 Panels API.

NOTE: This will probably be the last release of the 5.x-1.* series, which will soon be deprecated. Sites should consider migrating to the 5.x-2.* series (especially once 5.x-2.6 is out).

Changes since 5.x-1.0:

• #321653 by shane_jordan: Fixed bug where if a signup administrator canceled an anonymous signup on a given node, all of that anonymous user's signups were also canceled. This bug was from the original implementation of anonymous signup support (#68497).
• #219680 by dww: Fixed bug where the email address of users who signup was being sent in the notification emails to event owners, which is an inadvertent disclosure of personal information. Now, only a link to the user's profile is included.
• #137609 by dww and stBorchert: Added a lot more themeability for how the site-specific custom signup data is displayed for the signed up user, the signup administrator, and in the email messages. This also fixes a bug (#178441) where the labels for the custom fields were not included in the email messages.

This release is the culmination of a tremendous effort clearing out remaining issues in the Drupal 5 code base on the way to the port to Drupal 6. It includes a number of bug fixes, including some potential information disclosure bugs that should be carefully considered (listed separately).

In terms of new features, the biggest new feature is massively improved themability. There's a list of all the new theme functions added in this release to help site builders quickly see all the new opportunities for customization. Another key new feature is a default view of all the users who signed up for a given node, and various settings related to how this information is displayed. The other most noteworthy feature is optional integration with the token module. Huge thanks to Greg Mount for the generous donation to the signup fundraising effort, and everyone else who contributed. Also, special thanks go to deviantintegral and stBorchert for all their help with patches and testing.

Bugs fixed since 5.x-2.2:

• #169372 and #171363: Fixed bugs with redeclaring functions caused by using include() instead of include_once(). NOTE: This bug mostly showed up as SQL or other errors when trying to run cron.
• #179540 by dragonwize and dww: Restored the login/register links for anonymous users when viewing a signup-enabled node.
• #181627 by stBorchert and dww: Removed an inappropriate WHERE clause in the signup UID views argument handler that restricted the query to nodes where signups where open. That should be handled via a filter.
• #183417 by dww: Switched to a better method for conditionally including views support code. This no longer uses signup_init(), which wasn't necessary and made this module listed as incompatible with aggressive caching for no good reason.

New features since 5.x-2.2:

There are 2 major changes since 5.x-2.0: a long-awaited new feature, and a critical bug fix for anonymous users:

• #32482: Adding support for signup limits per node:
  • New field on site-wide signup defaults and per-node edit form to set or modify the signup limit.
  • Signups auto-close when the limit is reached.
  • Users can now cancel their own signup when signups are closed, and if it's not an event-enabled node, or the event hasn't started yet, signups automatically re-open.
  • Cleanup of the node/N/signups UI.
  • Even bigger cleanup of admin/content/signups UI.
  • Views support updated to view and filter by signup limit.
• #138401: Fixed a fatal PHP error on certain pages for anonymous users when caching is enabled.

The first official, stable release of the signup.module that is compatible with the 5.x core API. This release includes all of the bug fixes mentioned in the 4.7.x-1.1 release, so please see those release notes for more details. In particular, 5.x-1.0 includes the same database update from 4.7.x-1.1 that renames the permissions defined by the signup.module. Sites upgrading to 5.x-1.0 directly from 4.7.x-1.0 should therefore be sure to run update.php.