I’ve been working on creating a way to integrate registration forms into a library's website. It’s a lot more difficult than you think since I want the following features:

  • The event creator can set a limit on how many people can sign up
  • Custom fields for each node's forms (I probably need around 15 different reusable registration form types)
  • Instant email confirmation sent to the user’s email account
  • An email reminder to be automatically sent out 24 hours before the event
  • Ideally I'd like to set up a text message system as well.
  • The ability for the event creator to look at a list of everyone who has signed up
  • Ideally this would be exportable into a spreadsheet.

I'm not familiar with the Ubercart and Webforms modules, but this looked like it might be a helpful module to help this non-profit create event scheduling.
I tried to use the Signup module but it looks like it's too difficult to hack to create custom fields. Right before I left work, I started to try out CCK Signup which turns out to have next to no documentation on how to get it to work to notify users.

I appreciate your insight!

Comments

AndyF’s picture

Status: Active » Postponed (maintainer needs more info)

Hi,

I'll try and help as best I can. I can't promise that this module offers the best way to achieve your goals, but I don't know of anything better.

The event creator can set a limit on how many people can sign up

webform can handle that.

Custom fields for each node's forms (I probably need around 15 different reusable registration form types)

That fits in nicely with the webform philosophy - each registration form can be a different node of the webform content type. What can be frustrating is that there's no way (that I know of) to share components between webforms (eg. on every form the personal information will consist of three textfields, for name, email address, and phone number) which can lead to annoyingly repetitive creation of forms.

Instant email confirmation sent to the user’s email account

webform can handle that

An email reminder to be automatically sent out 24 hours before the event

I'm not sure what the best way to do that would be. I wonder if you couldn't do something using rules; but there may very well be a contrib module that offers precisely this functionality. If it came to it, it wouldn't be particularly difficult just to do a custom cron run that sends out appropriate notifications.

Ideally I'd like to set up a text message system as well.

I've never used it, but you might want to look at using a messaging API such as Notifications.

The ability for the event creator to look at a list of everyone who has signed up

webform can handle that

Ideally this would be exportable into a spreadsheet.

webform can handle that

Let me know if you have any more Qs.

HTH

Hanscraft’s picture

Wow, you are amazing! *beams*

Unfortunately, I'm super tired right now so I'm not processing correctly. In the meantime I can tell you that since then, I've managed to do the following (just for your expanded knowledge):

* Create an Event and Signup content types and link them via node reference.
* When someone signs up (creates a new Signup content type), a confirmation message is sent to their phone. This was done via Rules, Notifications, Twilio, and SMS framework.

I'll revisit your super helpfulness when I'm more awake!

AndyF’s picture

Glad it was helpful! Good job on getting the SMS sorted - out of interest, how come you needed Notifications _and_ SMS Framework? (I've not used either before.)

Hanscraft’s picture

These are the primary links I used to help me set up SMS:

http://codekarate.com/content/sms-drupal
http://drupal.org/node/1127346

The second link listed using Notifications and the SMS module. From what I understand of the mechanics, notifications can send out a variety of messages while SMS Framework gives you the structure to send those messages via SMS.

I'm going to try setting up a webform today to see what I can do!

AndyF’s picture

Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.