Event Calendar v3

[LaCamus]

This add-on provides some BASIC event management functionality, and yes there is some flexibility within these BASIC functions. However, this add-on still does NOT TRULY support a single event spanning over multiple days where each day has a different start/end time, and it really doesn't include features which would make selling tickets to such an event possible.. To do this would require a substantial re-write to this module to support it, not the least of this being that there are no start/end time fields currently..

I think multiple times could probably be coded in a few days. As for the selling of tickets, this could be easy (after the ability to create multiple times per event is added), that is if you just want to link a start and end time to a product...it's the additional info that could be needed that becomes problematic. Like seating, collection of personal info (say for seminars), availability (sold out)...but in truth all of that should be a separate module on the product side (possibly a few new product types?). The event calendar should really only provide dates, times and links to info and products...2 enhancements that would be helpful when handling things like concerts or seminars would be to show availability on the event page (by using the count of the linked product remaining in stock...an existing field) and the ability to group events (think something like Jazzfest in New Orleans that covers multiple days over multiple weekends) so that all dates and times for that group could be viewed on the same page.

and YES I know that one could come up with a way to work around this and create something that works, but a workaround doesn't make this add-on capable of this kind of functionality. In fact having to use a workaround to fill in for a missing feature only serves to highlight that this add-on just doesn't contain these features..

if someone knows of a workaround explain it to me, I am interested in this so I can understand the exact functionality you are looking for.

Adding start/end time or any other fields doesn't mean that one HAS to enter this data. Clearly if it doesn't apply, then don't fill it out.. Adding a field doesn't make it a REQUIRED field, and it is very possible to write the code in such a manner that non-required fields that do not contain data need not be displayed on the event page.

Right...I'm thinking it would be a popup that would allow you to add multiple start/end times that could span across any of the dates within your start and end date range. An example (again) would be Jazzfest, on Friday from 7pm to 9pm on stage 2 link it to tickets for concert #1, on Friday from 11pm to Saturday 1am on main stage link to tickets for concert #2...etc. Add as many of these time slots as you like, or none at all.

Right now the only way to achieve creating something resembling a multi-day event where each day has a different start/end time with this add-on is to enter multiple single events. That said, I never said that the recurring events functionality was meant to bring this functionality to this module (it doesn't), but it does make it possible to easily enter something resembling a multi-day event by allowing one to enter multiple single events (so that EACH day can have it's own start/end time).

Rus

[LaCamus]

Right...I'm thinking it would be a popup that would allow you to add multiple start/end times that could span across any of the dates within your start and end date range. An example (again) would be Jazzfest, on Friday from 7pm to 9pm on stage 2 link it to tickets for concert #1, on Friday from 11pm to Saturday 1am on main stage link to tickets for concert #2...etc. Add as many of these time slots as you like, or none at all.

...this also allows for having overlapping times. Say two concerts going on at the same time. For seminars you may want to open up another one in another room at the same time if the event becomes popular and sells out.

[DivaVocals]

I think multiple times could probably be coded in a few days. As for the selling of tickets, this could be easy (after the ability to create multiple times per event is added), that is if you just want to link a start and end time to a product...it's the additional info that could be needed that becomes problematic. Like seating, collection of personal info (say for seminars), availability (sold out)...but in truth all of that should be a separate module on the product side (possibly a few new product types?). The event calendar should really only provide dates, times and links to info and products...2 enhancements that would be helpful when handling things like concerts or seminars would be to show availability on the event page (by using the count of the linked product remaining in stock...an existing field) and the ability to group events (think something like Jazzfest in New Orleans that covers multiple days over multiple weekends) so that all dates and times for that group could be viewed on the same page.

You are right event ticket sales SHOULD be handled as a new product type. The event manager is meant to create/manage events. However linking a product to an event product doesn't have to require a new module persay.. It WILL require a custom product type to manage all the data collection that comes with event sales. ie: Like collection of personal info (say for seminars), etc. Availability doesn't require anything new.. It can be managed using default Zen Cart inventory management features.. set the inventory level for your event product to the number of seats available.

The custom module I had built allowed me to link an event to an existing "regular" product/category/manufacturer (not unlike this module). However if I wanted to create a NEW event product so that I could sell tickets to that event, I could do so from the event manager. Creating an event and adding an event product in one workflow is much more efficient from a user POV versus making the user create the event product, then create the event and THEN link the event product to the event.. In my custom event manager, the high level workflows for this was as follows:
One Day Event Workflow
Create an event
Set the start/end date
Set the start/end time
Set location (locations were managed as part of the Event Manager)
Link a "regular" product/category/manufacturer
OR
Create a product to sell tickets for this event. (the event product would be linked to the event at the end of the workflow)

Multi-Day Day Event Workflow
Create an event
Set the start/end date
Set the number of days this event spans
Set the start/end times for each day
Set location (locations were managed as part of the Event Manager)
Link a "regular" product/category/manufacturer
OR
Create a product to sell tickets for this event. (the event product would be linked to the event at the end of the workflow)

Ticket options (like child ticket vs adult ticket, register for one day versus three days of a three day event) were managed using the default attributes features build into Zen Cart. We used a little custom code to manage things like early bird registration discounts based on the day tickets were purchased (discount was a field set on the event product type).. Free events which still required registration simply meant that we created a zero dollar product. As for locations my custom module was not setup for managing specific seats (like in the concert venue example). My custom module was designed more for organizing camping trips, little league registrations, seminars, tradeshows, and other similar type of events. So locations contained addresses, Google Map info, phone numbers, hours of operation, etc.

Now my custom module also managed RSVPS and had other guestlist management functions which I am NOT suggesting should be added to this module. In fact I am not really suggesting any of the stuff I'm talking about should be added RIGHT NOW.. I think what's in place right now is good enough to submit once these last few cleanup items are addressed.. However, I am saying that in order for this module to become something mature and really feature packed it should be the direction/roadmap that this thing SHOULD be headed for eventually..

if someone knows of a workaround explain it to me, I am interested in this so I can understand the exact functionality you are looking for.

Right...I'm thinking it would be a popup that would allow you to add multiple start/end times that could span across any of the dates within your start and end date range. An example (again) would be Jazzfest, on Friday from 7pm to 9pm on stage 2 link it to tickets for concert #1, on Friday from 11pm to Saturday 1am on main stage link to tickets for concert #2...etc. Add as many of these time slots as you like, or none at all.



Rus

There is no workaround for this.. I can SIMULATE a multiple day event by creating multiple single events that have the same title/description with the different dates.. but I would have to enter the start/end times in the event description, and I could jerryrig up an event product to sell tickets using attributes, but it would only work for very simple events, and there would be no way to register multiple registrants for an event like a seminar. Each registrant ticket wold have to be purchased separately or you'd have to rely on folks using the order comments to enter registrant data.. Bottomline it would be error prone and messy..

...this also allows for having overlapping times. Say two concerts going on at the same time. For seminars you may want to open up another one in another room at the same time if the event becomes popular and sells out.