Forum Replies Created
-
Posts
-
It’s possible that there’s a conflict. Although I’m sure what your doing is all in order can I just confirm the sort of search you are doing?
Is it for a word or words that appear in the title or description, for instance, or are you trying to search against date fields or anything like that?
Hey John – it’s something that a number of people have already asked about, so it will be seriously considered. At this early stage however I can’t definitively say Yes or No, nor even can I suggest a tentative timeline.
That could change at any time however so please do feel free to subscribe to our newsletter and blog to stay abreast of developments 🙂
Hey everyone, thanks for these great questions!
In the demo it shows that the ticket purchaser must enter their full address. This seems unnecessary for someone registering for an event and receiving the ticket over email.
So with WooTickets we are joining together two different plugins, The Events Calendar and WooCommerce. Each plugin has different responsibilities and in this case a customization to change the checkout procedure is on the WooCommerce side of the fence.
What I can say is that tickets are automatically categorized (I believe within a category called tickets) so you could introduce code that sits and watches for those kinds of purchases and modifies the checkout process appropriately.
For more on this kind of thing I would suggest visiting the Woo forums and documentation.
Do purchasers have to pay through paypal or check, or can this addon take credit cards?
The default payment modes are those that ship with WooCommerce. If you visit their website you can see that numerous other payment and shipping gateways are available for you to purchase.
Are there any features that eventbrite has that this does not?
Beyond the possible advantage (in Eventbrite’s case) of being a large scale web app that might be better suited to handling large amounts of traffic, in addition to their own suite of reporting tools – which may or may not be better than those provided by WooCommerce – I can’t really think of any significant differences on a big picture level.
(But see my answer to John’s question re recurring events, further down.)
If you purchase the add-on and realize it won’t work for your needs, are refunds offered?
Yes, with all of our plugins you are welcome to email us with your refund request. Generally there is no problem here, but it is decided on a case-by-case basis.
Does WT support recurring events with custom dates like eventbrite does?
No unfortunately at this time recurring event support is not included (nor is it for our Eventbrite Tickets plugin, though the Eventbrite themselves do support this).
Can you register and pay for multiple events in one transaction? Or can you only sign up and pay for one at a time?
Tickets are effectively products and are treated as such by WooCommerce, so you can add multiple tickets to your cart and change the quantities – just as you would generally with WooCommerce.
I hope that answers all of your questions but please don’t hesitate to get back to me if you need clarification on anything.
Thanks!
Well, normally you don’t need to add any additional code – if the additional field has been specified then it will be displayed as part of the standard single event template.
So I’ll close this off now – but do feel free to create a new thread if there is anything else we might be able to help with.
Hi Sean, from the sounds of it (@codearachnid is indeed one of our devs) yes that is likely to be addressed as numerous aspects of the plugin are being overhauled in time for the next major release.
Hi Alistair!
Perhaps you are confusing the custom fields functionality provided by WordPress with the Additional Fields feature built in to our plugin (that can be configured from Events > Settings > Additional Fields and then set in events meta box)?
If you want to use WordPress’s custom fields (I’m guessing that is what you are trying to do, based on the screenshot – let me know if I’m off-beam here though) then you should use the functions made available by WordPress to display them rather than our template tags.
Does that help?
That’s a big leap and it’s generally better to update incrementally. What I’d suggest as a minimum is initially updating to 1.3.3 and then once that is complete update to 2.0.9, observing all the usual advice about updating that you might find in our docs.
Most importantly, back-up and know how to restore that back-up! You can grab 1.3.3 here:
Hi Tony – think we addressed this in another thread but just for completeness, that capability is currently lacking but I’ve added it to the list of possible improvements for the devs’ further consideration.
Thanks again!
No problem at all, it’s the first public release and it’s great to have so much fantastic feedback and feature requests to take forward.
Ah OK, well one of my team members or I will try and get an answer to you in that thread shortly. Certainly it sounds like Tim (@codearachnid) is aware of the issue and some notable changes are indeed pending.
Since we’re all set here though, what I’ll do now is close this thread.
Glad you’re sorted on the undefined function error 🙂
