I would like to let my users reserve seats (or a whole table) for events, and pay for the reservation via PayPal.
Different performances/shows would be advertised, users could choose which tables or seats they would like to reserve. A theater OR bar, restaurant, etc. would have "fix" seats and tables, so they would not change (or just rarely); events can be repetitive/recurring (e.g. concerts) - in some cases, locations can remain the same too, so only the date changes (e.g. a concert played in Example Bar 3 times a month); but one event can be played in other locations too.
I tried on Drupal.org first, but I got no answer; any help would be appreciated.
If there's no way to "bind" it to Ubercart, I'd solve it in another way (PayPal IPN), but I have to do it ASAP.
P.S.: I've already tried MERCI, Simple Reservation, Hotel Booking System for Ubercart and Reservation modules (the latter seemed OK from the picture), but unfortunately I couldn't figure out how to do something similar to what I need - BUT THIS MEANS NOTHING, maybe I just overlooked some opportunities!!!
If you say I can solve it with one of these modules, please help! Even if you have a totally different suggestion! Thanks!
In the meantime I found this very interesting article: Ubercart Event Registration
Let me quote from it:
at the moment, the de facto Ubercart method for doing online event registration is with a module called UC Node Checkout. It's perfect for a one-and-done event registration site, but for a site that is hosting several events simultaneously and on an ongoing basis, it's awkward. This is due to the fact that it maps a content type to a product SKU - so for each event you'd need to create a new content type. Not really very good long-term, particularly when the site administrator is not overly familiar with Drupal or Ubercart.
So, an alternative solution was devised using the Webforms module. The webform stores the registrant's organization's information - and also asks the registrant how many tickets to the event they want, which is the use case the client specified. The webform, after processing the form, adds the event 'tickets' to the cart. This is done with the 'Webform advanced settings' field in the webform configuration, under 'Additional Processing'.
Good to know. This means the article I found earlier doesn't describe what I need.
Another quote from uc_event_registration's readme:
UC Node Checkout
This is the approach that has been used alot for Drupal conferences and demo'd at drupalcons. The huge problem here is twofold: First, registrations are nodes. That means we have to build views to create registration lists and that seems like unnecessary overhead when Webform is so much lighter weight. Second, and most importantly, you need a new content type for EVERY event. No thanks. On sites that are doing dozens of events per year, this would mean, eventually, a huge amount of content types. That's bad.
Here's another one related to Webforms: Drupal Webforms With Dynamic Select Boxes Tutorial
This seems very promising, maybe this could be the way one could solve what Andy suggested.
I'm still interested in suggestions for practical solutions - maybe this way!