Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
This release fixes a critical bug in 1.1. In earlier versions, the lookup table was rebuilt on every failed lookup on the logic that you're unlikely to actually trigger a lookup unless you actually had data. However, I discovered that was causing dozens of cache_set() calls per page, which is doubleplusungood. This version uses hook_flush_caches() to rebuild the lookup table instead, which is really should have done in the first place.
#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.