signup

Last Saturday August 1, members of the Hackerspace Brussels gathered to build a job database for the NGO Zuiddag.

I just got the following email when I signed up for an event in the Waterloo Region group:

Thanks deviantintegral@drupal.org for signing up for our event. You will be reminded 1 day before the event.

Troubleshooting performance issues on a slow web site
[Untimed]

%info

This might be a bug with signup itself, but I haven't seen such an issue on any of my own sites running Signup.

I just released an install profile for D6 core that sets up a test site for trying out all the combinations of CCK date field configurations: CCK Date Testsite. I've discovered various bugs in Signup's handling of CCK date fields (and have been fleshing out bugs and limitations in DateAPI itself with KarenS's help). I was spending a lot of time just configuring a reasonable test site to try different combinations of CCK date field types (Date, Datestamp, vs. Datetime) and timezone handling (there are 5 different ways date fields can handle timezones). So, I quickly decided the time spent automating the test site would easily save me time in the long run. And, I hope this profile will be useful to other folks working with DateAPI and CCK date fields.

After a successful fundraising effort and a lot of hard work, I'm pleased to announce that the Signup module has made some major leaps forward in the recent past:

• Supports CCK date fields for reminder emails and auto-close functionality (#86462). You can have both event and date enabled on the same site. For CCK date node types, you select which date field you want to use for signup functionality when configuring the node type.
• Ported to Drupal 6, Views2, etc. The 6.x-1.0-rc1 release candidate is now out.

There are a ton of other improvements too numerous to list here. For details, check out the 5.x-2.6 and 5.x-2.5 release notes.

Hi,

I've been trying to get my head around getting signup into my panel-modified display of an event node.

Ideally i'd like to get both the signup form and the attendees into one of my panels but I can't figure out how it's done without support for panels from signup.

What's the best way to create an attendees list? Since they're not nodes, I can't create them through views and then feed them into my panels that way.

Am I missing something really basic?

Cheers,

James

FYI: I started a ChipIn to raise money to improve the Signup module and port it to D6. The development goals that will be accomplished if we raise the money are: a) drive the CCK integration patch home, b) do everything else needed for a 5.x-2.5 release, and c) port to D6.

My appologises if this has already been discussed but I was wondering if there is a patch (or otherwise) which allows the signup schedule module to more exactly specify the opening and closing time than just midnight on the said day. And if there isn't I was hoping someone would be willing to create said patch as I think it would be very useful for event signups to give more control over the signup period.

I'm thinking about using the signup module for an online class registration process, but I really need a waiting list feature when the classes reach capacity. Has anyone worked on a feature like this, for signup or anything else?

I found one mention of a wait-list feature here: http://groups.drupal.org/node/4151 but haven't stumbled across it anywhere else. Has anyone else had a need for this feature? I'm open to suggestions, or better alternatives than working with Signup, if anyone has any ideas for me.

Thanks!
Jen

I maintain the signup.module. This module has long struggled with the problem of how to flexibly define what fields are requested and/or required when a user signs up for something. I might have a slick solution, but I'm not sure if CCK can accomplish what I have in mind.

With 5.x CCK, you can assign any fields you want in whatever groups you need to any node type. My module could allow site admins to define the signup/reply form for any given node type as a specific group of arbitrary CCK fields. This field group would not show up on the node edit form. It would be displayed on the node view page itself, so each user could fill-in, submit, and optionally edit their own signup/reply. All fields would automatically be treated as "multiples" in terms of storage, 1 set of each field's values per user who replies, but displayed as single values for any given user viewing the node. When a user replies, the values of any fields in their reply would have to be associated with their identity (uid for auth users, email for anon).