At long last, an official 6.x-1.0 release. ;) Huge thanks to ezra-g for stepping in as a co-maintainer and doing a flurry of activity to clean up the DRUPAL-6--1 branch in preparation for this release!
One of the biggest changes since signup 6.x-1.0-rc6 is that Views is now a required dependency. If you don't already have views enabled, you will need to install and enable views before upgrading to this release. Due to a bug in core that was never fixed for D6 you will not be able to enable views from the admin/build/modules UI once you install signup 6.x-1.0.
The 6.x-2.* release series is a fairly major rewrite of the signup module by joachim from #29568: Flexible number and type of fields. dww has not reviewed any of this code. This branch is not compatible with the UberCart Signup module. If you want to use uc_signup, stay with the 6.x-1.* series.
Once again, I've been naughty and I'm introducing API and schema changes here in a "release candidate". Sorry about that! However, ultimately, they're for the best, even if it's a slightly bumpy ride right now.
Sites using Signup status which are attempting to make use of the "Modifies signup count" setting for any status codes will be happy to know that upgrading to this release and 6.x-1.0-alpha2 of signup_status will make feature actually work. However, sites using Signup status should upgrade to signup_status 6.x-1.0-alpha2 and run update.php before upgrading to this release (although you need to upgrade to signup rc6 before signup_status alpha2 will actually work).
#439294 by dww: Fixed bug where %user_signup_info was not being replaced with an empty string on sites that do not define any extra fields on the signup form.
#539052 by dww: Fixed jQuery bug when users edited their signups that was causing most of the form elements to be enabled before pressing the 'Edit' button (all form elements should be disabled at first).
#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.
#370397 by ezra-g: Fixed critical data-loss bug where all anonymous signups would be destroyed if any authenticated user was deleted. This bug was introduced during the port to Drupal 6 core, due to an undocumented API change between Drupal core versions 5 and 6.
#350548 by dww: Fixed logic bug in the support for Event module which would close signups prematurely if you edited event nodes in the future.
#354944 by stBorchert: Fixed bug where changes to signup settings were lost during node previews (in Drupal 6.x only).
#350872 by gargoyle and dww: Fixed bug where node type names were used unquoted as table aliases in the SQL for the admin/content/signup page. If you had a node type named after an SQL reserved word (e.g. 'match'), you'd get SQL errors. Now, node type names are properly quoted.
#181272 by dww: Fixed bug where the labels on the custom signup form fields were not properly translatable when this data was displayed in other places (when viewing your own signup info, etc).
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.
#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.
#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 5.x-2.4 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-5--2 branch (check the top of your copy of date/date.module and make sure the revision is at least "1.39.2.50" (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.
#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.
The major new feature in this release is #86462: support for CCK date fields to control the time-based signup functionality (reminder emails and auto-closing signups a configurable number of hours before the start time). You can have both Event module and CCK Date enabled simultaneously, and the 5.x-1.* and 5.x-2.* versions of both modules are all supported. As a result of this change, the word "event" no longer appears in the UI unless specifically referring to the Event module. Therefore, the hard-coded tokens you can put in the email templates (e.g. for confirmation and reminder emails) have been renamed. Be sure to visit update.php after upgrading to this version and run signup's update 5204 which will convert all of your saved email template settings to the new tokens.
In other news, the per-node signup administrative tab got a nice UI improvement thanks to #333257, and you can now embed the signup form as a pane when using Panels thanks to #321531. This release also fixes a number of bugs and includes some other changes detailed below.
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).
#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.
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.
After many months of unfortunate neglect, the singup.module has recently gotten a round of major attention and improvements. Mostly, the changes below are bug fixes, but in a few small cases, some new functionality was added, as well. This release includes a database update, which renames the permissions this module uses, so be sure to run update.php on your site, and then visit your 'access control' page (at /admin/access) to ensure the signup-related permissions are valid for the roles defined on your site.
The DRUPAL-5 branch of the signup module is now in a feature freeze, in preparation for a stable 5.x-1.0 release. Very few (if any) new features have been added since the DRUPAL-4-7 branch, but lots of bugs have been fixed, and the code has been ported to the 5.x Drupal core API.
An official 5.x-1.0 release with more detailed release notes will be available as soon as enough testing results come in. Please see http://drupal.org/node/123689 for more information.
Initial official release from the stable 4.6.x-1.* series. There have been no changes in the signup module since August 2006, so this should be the same code as any of the signup-4.6.0.tar.gz files from 2006-08-19 and later. Additional releases of this series will only fix bugs in the existing functionality.
Initial official release from the stable 4.7.x-1.* series. There have been no changes in the signup module since August 2006, so this should be the same code as any of the signup-4.7.0.tar.gz files from 2006-08-19 and later. Additional releases of this series will only fix bugs in the existing functionality.
The 5.x-2.* series is where new features that are compatible with Drupal core 5.x are being added. For full details, either see the release notes for the official releases in this series or the CHANGELOG.txt for this module.
