Forum Replies Created
-
Posts
-
Hey Martin. Happy to answer these questions for you. Thanks for your interest in the products, too.
For your first question: the way WooTickets works, tickets don’t appear in the shop by default. They’re only going to appear within actual event entries out of the box; so if you weren’t utilizing the calendar component, it might not be a good fit since the events angle is a huge component of how WooTickets operates.
There aren’t QR codes or anything like that at this time, though we’ve had enough demand for it that we’ll likely be incorporating that down the road. At this point we do have a unique checkin code that comes with each ticket, though, as a way of verifying a user’s ticket against the broader attendee list.
That help? Let me know if not, and I can elaborate on this for you.
Hey Nathan. If you wanted to accomplish all three of those angles – frontend submissions, ticket sales and a calendar with recurring events – those three would probably be the best batch. If you don’t need recurrence and the other PRO features detailed here (https://theeventscalendar.com/shop/wordpress-events-calendar-pro/), then you could drop PRO from that list and just run Community/WooTickets on the free, core The Events Calendar plugin.
My experience with WooCommerce is rather limited to the way it interacts with WooTickets; but from what I can see at that link, my guess is it’d require some customizations to build that widget into the sidebar. WooCommerce may well have some widget components (unrelated to WooTicktets) that can help get you there, but I sadly haven’t ever used those. That said: remember that WordPress does have their simple text widget, so if you could craft some HTML that accomplished what you’re going for via a homemade customization, it’d probably work. But I can’t guarantee anything.
That help? Let me know if not, or if you have other questions.
Hey Ben. Thanks for the note here, and for reporting this issue. We can definitely help you out here…but mind posting a new thread in the PRO forum, so we can have the PRO team hit it? This forum is for pre-sale issues and might not be the best place for it.
Thanks in advance. Once the thread is up, we’ll be in touch with haste.
Hey Derek. Good question; thanks for posing it. At this point: no. We’ve had a lot of requests for that and may well incorporate it either in WooTickets or a separate add-on down the road, but at this point no such functionality exists.
Hope that helps and sorry I couldn’t give the answer you were probably looking for here. Any other questions? Let me know and I’ll get you what you need.
Hey Lorenzo. Thanks for your interest here. We were originally intending to bundle the CSV importer with the original 3.0 release (as a core feature), but development / feature creep forced us to re-evaluate that. We are definitely still planning on implementing and integrating into one of the first post-3.0 releases (likely 3.1) but it’s not going to ship with the initial build.
Hope that helps and sorry I couldn’t offer anything more. If you have other questions, let me know.
Hey David! Thanks for posting this. Looks solid and I’m going to attempt to recreate today. Can you do me a favor, though, and – as Barry noted – keep your feedback to email for the time being? We’re not handling 3.0 beta support here on the forums…just 2.0.11 stuff.
If you want to email me (rob /a/ tri.be) I will definitely follow-up with you based on my tests to share the results. Thanks again!
Hey Steven, thanks for the words! Glad to hear you’re enjoying the plugin so far.
We’ll do our best to help you out on that dot-org forum you posted. But otherwise, if you buy WooTickets and need help, we won’t deny you that based on the fact that you don’t have a PRO license. My attitude is if you’ve gone to the extent to buy an add-on that extends The Events Calendar/PRO, it’s only right that we help make that work so you can ensure the add-on works too. And if you find that the level of support isn’t satisfactory we would be open to a partial/full refund based on whatever you felt was fair.
Hope that helps. If it doesn’t, or if you have other questions, just holler.
Ah after some further digging with the team on this, it looks like a caching system we implemented on the tri.be site broke our shop API, which is causing this message (it just reared its head today because we made the change last night).
As a temporary workaround, you should be able to get rid of the message by using the hide_upsell option in your wp-config file. Specifics on that are here: https://theeventscalendar.com/removing-the-add-on-upsell-in-events-calendar-pro/.
We’ll get this issue resolved as soon as possible. Thanks again for the tip.
Thanks for the heads up here, guys. I just talked to the dev team on this and it’s a weird issue, particularly because both of you are seeing it.
Can you guys confirm that you’re both on a stock Twenty Twelve install, running just The Events Calendar 2.0.11 with no other add-ons? Would also be interested to hear your hosting setup: if you’re using a standard provider, or if you’re doing locally, etc.
This hasn’t come up before and best I can tell it isn’t impacting functionality – just throwing out those warnings – but let me know if I’m wrong there. I do want to see what can be done to find a resolution for you here so let me know about those questions and we’ll troubleshoot from there.
Ah, sounds good! If you dig anything up there, or need us to take another look, definitely let me know.
Hey Rob! Thanks for the follow-up. Glad to hear that helped. Yes, if you find that the PRO release or WooTickets do not allow you the level of customization you’d hoped, I can refund you for them. All I ask is that you try to work through the issue with our support team here on the forums before taking that step…9 times out of 10, they are able to help get people there we want to be.
Hope that helps! Let me know if I can shed any more light on this for you, and thanks again for the interest.
Hi Nathan! Thanks for the note. Glad to hear you’ve got some interest in the PRO release.
You can include video and imagery in the event listings, yes. These are just a custom post type…so pretty much anything that can display in a regular post can be used on events as well. You can set an image (the flier, for example) as the featured image as well as include it within the entry as you see fit.
An RSVP/Purchase button could be added, definitely, but it’d require you to do a template override of the list view/single event view (more on template overrides here: https://theeventscalendar.com/what-are-template-overrides-and-how-do-i-do-them/). Keep in mind that if you were trying to actually implement an RSVP or ticket purchase aspect, you would need to either build that out buy another add-on like Eventbrite Tickets or WooTickets. The plugin doesn’t ship with a registration component by default.
In terms of additional functionality you’ve outlined…
* A user submitting their own event could absolutely be done with Community Events (https://theeventscalendar.com/shop/wordpress-community-events/).
* Selling tickets would be possible with either WooTickets (https://theeventscalendar.com/shop/wordpress-wootickets/) or Eventbrite Tickets (https://theeventscalendar.com/shop/wordpress-eventbrite-tickets/).
* We don’t have a booking component for the restaurant angle you noted quite yet, unfortunately. We’re discussing what it’d take to get us there right now and may well release an add-on that accomplishes this later on, but for now it’s not possible unless you build something yourself.Hope that helps. If it doesn’t, or if you have other questions, please do let me know.
Hey Eder. Thanks for pointing this out; I’m not seeing the same thing but I may be testing differently than you. This is in 2.0.11? And can you confirm what template setting you’re on, so I can try to recreate?
Hey there Tico! Thanks for the note, and for reaching out. That site is looking nice; sadly, our calendar as it stands does not have that dropdown built into the calendar. There is a widget that allows you to target events FROM a given category (as the admin), but frontend users don’t have an ability to filter down by categories themselves that way.
All this said: we’ve got both these options (category filtering and the ability to do so from the sidebar) coming with the 3.0 release. That’s on the docket and should be released over the coming weeks…so relief is in sight on this end.
Hope that helps. Let me know if it didn’t, or if you have other questions.
Hey Rob. Thanks for the note here, and for your interest on this end. Happy to help you out and answer these questions best I can. I’ll say right off the bat that you’d probably need to hack at the plugin or adjust WooCommerce settings to turn off the email follow-ups, as the tickets are autogenerated by default and kick out immediately when the purchase is completed. Also worth noting that, even though you don’t need the calendar itself, there isn’t really any way to hide that beyond strategically hiding the calendar link.
Assuming those aren’t dealbreakers, read on:
1. This would be doable if you were willing to do a template override to modify that template itself. That’d be a relatively straightforward process. However no button for the “buy” option appears in the list by default.
2. You could just make the “list” view the default and disable the frontend toggle button….that would give them the list view and no option to change to calendar (though if they knew the proper URL structure, ie /events/month, they could still get there).
3. The list should definitely be far more responsive than the calendar view. That said, we don’t have as much code to integrate with it in 2.x as we will in the upcoming 3.0. So while it should work decently enough in the current build, it’ll look much better in 3.0.
4. You can change this, yup.
5. You can absolutely style and customize the event descriptions. Since they’re just a custom post type, pretty much anything that works in a regular post should handle itself similarly in an event entry.
6. The book button here, like the one in #1, should be doable but not as an out of the box feature. A template override of the single entry sounds like it could get you there.
7. Since our tickets are just WooCommerce products (the plugin merely hooks into WooCommerce to leverage it), you should definitely have the same behaviors for WooTickets as you would for any other WooCommerce product on this end (except that they don’t appear in the ‘store’ by default).I believe that covers everything. But if I missed something, or if you have clarification questions, definitely let me know and I’ll follow-up as needed. Thanks again for your interest!
