Home › Forums › Calendar Products › Events Calendar PRO › Need to plan out Additional Features
- This topic has 12 replies, 3 voices, and was last updated 10 years, 8 months ago by
Brook.
-
AuthorPosts
-
July 20, 2015 at 1:47 pm #988125
Tojo John
ParticipantHi,
I need your help with adding features to Events Calendar Pro (I also have the Filter Bar Add-on). My inquiries are almost entirely related to registration/booking for events (like tickets) but there is no payment or e-commerce. We are the Harvard Club of New York. We have events that members can register for. Payments happen outside of the web-based interactions – so NO e-commerce (i.e. EDD, Woo or Shopp) needed.
We are open to custom programming (for extending) or buying add-ons. Your guidance on the right approach and possible documentation on implementation is appreciated:
On Member’s Side
———————————
1. Allow members to register for events (without e-commerce) and choose # of seats.
2. Get an email confirmation.
3. Allow members to cancel a registration.
4. Query and how a list of upcoming events the member has registered for.On Admin’s Side
——————————–
1. Set max # of participant for an event.
2. Set max # seats (party size) per registration (a member can reserve/book)
3. Set cancellation cut-off date/period.
4. Set email template for members’ registration confirmation
5. Have a Check-In Sheet for organizations to check in attendees on the day of the event. Export check-in sheet at the end of the day as Excel/CSV.Non Booking Related Feature Extension
————————————————–
1. Admin Sets Status of Events (could be done with meta fields)
2. Show a grid view calendar on the admin UI for event editors + Color code events in the grid based on Event StatusSorry for including a lot of items and if this is not specific enough. We really do need your help to meet our requirements for managing events for the club.
Thanks,
Miah MorshedJuly 23, 2015 at 4:44 am #989272Brook
ParticipantHowdy Miah,
I must apologize. I am sorry for our late response. Your topic’s status was marked incorrect and was thus lost from our queue for a spell.
We are the Harvard Club of New York. We have events that members can register for. Payments happen outside of the web-based interactions – so NO e-commerce (i.e. EDD, Woo or Shopp) needed.
That sounds good. In looking over your needs you might still be interested in WooCommerce Tickets or Easy Digital Downloads Tickets. Both of those allow free events/or events where the purchase was made separate. So you won’t have to setup payment features or anything, you can just use them as basic event managers.
On Member’s Side
———————————
1. Allow members to register for events (without e-commerce) and choose # of seats.
2. Get an email confirmation.
3. Allow members to cancel a registration.
4. Query and how a list of upcoming events the member has registered for.WooCommerce Tickets does both 1 and 2.
#3 is probably less automated than your are picturing. People can cancel but they will have to send you an email and you will cancel on their behalf.
#4 Is basically built in. The Woo My Account page is where a customer can view all past orders.
On Admin’s Side
——————————–
1. Set max # of participant for an event.
2. Set max # seats (party size) per registration (a member can reserve/book)
3. Set cancellation cut-off date/period.
4. Set email template for members’ registration confirmation
5. Have a Check-In Sheet for organizations to check in attendees on the day of the event. Export check-in sheet at the end of the day as Excel/CSV.1, 2, and 5 are features of WooCommerce Tickets. #3 will be handled manually anyways, so that is also doable. I am not quite sure what you mean by #4. You can specify the email template for all automated emails such as order receipt and the email which contains the ticket/code to use while checking in.
Non Booking Related Feature Extension
————————————————–
1. Admin Sets Status of Events (could be done with meta fields)
2. Show a grid view calendar on the admin UI for event editors + Color code events in the grid based on Event Status#1 is definitely a feature of our calendar. #2 is not. You could certainly write a customization to do that though. A similar one has already been written by a community member for colorizing categories: The Events Calendar Category Colors.
Does that all make sense? Does it answer your questions?
Cheers!
– Brook
July 23, 2015 at 7:04 am #989311Tojo John
ParticipantBrook,
Thank you for the reply. Based on the requirements I listed above and easy of integration, do you have a recommendation on WooCommerce vs. EDD?
Thanks,
MiahJuly 23, 2015 at 9:41 am #989480Brook
ParticipantWooCommerce is by far the most popular shopping cart. Because of its popularity it often gets features first. For instance, we are building out a ticket scanning solution where you can check people in at the door using a smartphone and scanning their ticket. This will come to WooCommerce Tickets first. So I think that would be my preference.
Cheers!
– Brook
July 23, 2015 at 10:05 am #989494Tojo John
ParticipantThat sounds good and thanks for the prompt response. You may not have answers for my next question but I will ask anyway.
Q. Do you have any idea on the time it requires to integrate WooCommerce + Events Calendar Ticketing to a site (no payments)?
Q. Are the UIs in WooCommerce made to be responsive?
Q. We are seriously considering creating a custom Post Type (with relationship) to collect/hold registrations for The Events Calendar events for quick development with minimal bells and whistles. Would you recommend against that?
Miah
July 24, 2015 at 1:14 pm #990093Barry
MemberHi Miah,
Brook may be out for the day so I just wanted to pop in and offer up a few possible answers 🙂
Q. Do you have any idea on the time it requires to integrate WooCommerce + Events Calendar Ticketing to a site (no payments)?
Very little!
Install and activate both WooCommerce and WooCommerce Tickets (alongside The Events Calendar, of course) and all you need to do from there is create some events and add the tickets!
Q. Are the UIs in WooCommerce made to be responsive?
I can’t vouch for all of them, but they generally seem to work well within the framework of a responsive WordPress theme. What I’d recommend is posing this question to the WooThemes team if you need more detail (at the end of the day, WooCommerce is their product and they are best placed to guide you on that front).
Q. We are seriously considering creating a custom Post Type (with relationship) to collect/hold registrations for The Events Calendar events for quick development with minimal bells and whistles. Would you recommend against that?
Well, that’s really something you have to weigh up and decide for yourself. A critical advantage to purchasing something like a WooCommerce Tickets license is you get access to a mature and well tested product – for which numerous support resources already exist.
Of course if you can develop something in-house that meets all of your needs in a short space of time/for a low cost, that’s great and is worth considering 🙂
I hope that helps!
July 31, 2015 at 7:50 am #992119Tojo John
ParticipantBefore we close out the ticket, I have one more issue to request your help on. After discussing the UX, user workflow and other business requirements with the Harvard Club staff, it seems that developing a custom registration (for events) is the right approach for them, instead of integrating an e-commerce system.
I wanted to ask if there are good documentation on hooks and best practices for developers who want to extend the plug-in features. An help/guidance on this would be greatly appreciated.
Thanks,
MiahAugust 3, 2015 at 8:28 am #992745Brook
ParticipantHowdy again Miah,
That sounds like a good plan.
Our code is very well documented. Every single public function is documented in the code and on the website. Many of our classes and their public functions have inline documentation as well. We also have a sizable Knowledgebase which has many tutorials and articles to assist with using the API.
Now I wish I could enthusiastically say we have everything documented, but there are is one weak area we are working to improve. We have an enormous amount of Hooks and Filters sprinkled in useful places, which makes it easy to develop for. But, at the moment we do not have a comprehensive list of them. Of course even without a list you can still find them the old fashioned way, but I do wish it was even easier than that.
Finally, we will be here as well to help answer questions.
Please let me know if you need anything else. Cheers!
– Brook
August 3, 2015 at 8:59 am #992763Tojo John
ParticipantThank you for the response. We will start developing this week on the custom event registration module. We are not creating an add-on or plug-in for it. We’ll simply create a child object (post type) to Events and then use front-end forms to allow our members to sign up for the events, which will dump the data to the new child object.
Is the knowledge base the only place you have your functions documented at this moment? Are there any other sources I should look into for documentation?
I will keep this ticket/topic open in-case we need to ask questions as we develop.
Thanks,
MiahAugust 3, 2015 at 5:32 pm #992932Brook
ParticipantHowdy Miah,
Is the knowledge base the only place you have your functions documented at this moment? Are there any other sources I should look into for documentation?
Our API documentation (AKA Technical Docs) is where the functions are documented. Our Knowledgebase on the other hand has tutorials and guides with practical examples of how to use our API. They are pretty tightly integrated, but still slightly different. The API Documentation is actually a curated version of our inline docs that exist in the code. The inline docs are the most extensive and can be found in context within each file of our plugin.
We’ll simply create a child object (post type) to Events and then use front-end forms to allow our members to sign up for the events, which will dump the data to the new child object.
That sounds awesome!
I will keep this ticket/topic open in-case we need to ask questions as we develop.
If you don’t mind, would you please open a new topic for each ticket? That’s part of our forum rules here. Our reasoning for this is not because we enjoy creating limitations. Rather, our tools here are built around a single issue per topic (IPT). Having one IPT means that we can track all issues and make sure every single one is resolved. It also means that users with similar issues are better able to search and find past topics because they all have unique titles. Finally and perhaps most important of all, we have found that a single IPT helps get our customers faster response times. 🙂
Please let me know if you have any more questions pertaining to this Miah. Cheers!
– Brook
August 4, 2015 at 9:21 am #993160Tojo John
ParticipantOK. I will close this post new topics. Thank for your help.
August 4, 2015 at 9:22 am #993162Tojo John
ParticipantOh! Didn’t realize the close radio is right on top of the comments box.
August 6, 2015 at 7:10 am #993874Brook
ParticipantYou’re welcome! Thanks for marking it resolved.
– Brook
-
AuthorPosts
- The topic ‘Need to plan out Additional Features’ is closed to new replies.
