Forum Replies Created
-
Posts
-
Hi, Pat. Thanks for your interest in our plugin suite.
Event Tickets Plus (ET+) is our paid add-on plugin that upgrades the functionality of our free Event Tickets (ET) plugin.
Event Tickets Plus enables you to sell tickets via one of our supported eCommerce platforms. The free plugin only enables free RSVP-type tickets.
You can view our roundup/comparison of all the eCommerce plugins ET+ supports.
Our plugin uses your eCommerce plugin of choice, but your eCommerce plugin isn’t displayed for shopping pages. Please reference our Making Tickets KB article (screenshots are from an install using WooCommerce) for an idea how to create tickets for an event.
Site visitors would purchase tickets from each event’s single page/view (e.g. http://wpshindig.com/event/events-tickets-demo/) — if there is an RSVP to submit or ticket to purchase.
The order confirmation email will include a QR code that can be scanned to “check in” someone at the door at the time of the event. It could be displayed on their mobile device or they could print it like any other email. You can read more at Tickets: Managing your orders and attendees.
If your tickets will be free, you don’t need QR code check-in, and you don’t need to collect additional information other than name and email address, you likely could just use the free/core Event Tickets plugin.
To limit the quantity available to purchase at a time, please reference these snippets:
https://gist.github.com/cliffordp/5b57df71be8b52f595817ddbf81acdab
and
https://gist.github.com/cliffordp/66bf05df61ee269c60ff20d6f39e2cab
The ability to pre-fill user data into basic ticket information is likely to be a future feature, but this Template Override example (https://theeventscalendar.com/support/forums/topic/populate-rsvp-form-if-user-logged-in/) could be helpful if you need such functionality right away.
Last but not least, we have a pretty great Refund Policy so you can buy one or many of our add-ons and thoroughly test them.
I hope this info helps. Let me know if you have any follow-up questions.
Ah ha! I did some extra digging and discovered that our Event Aggregator server (that does the getting and the heavy lifting) has an issue with its geolocation logic.
I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. My best guess is 1-3 weeks, but I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.
I apologize for this issue and appreciate your understanding and patience.
Hi, Steve.
Event Tickets Plus sends ticket products to the EDD cart but doesn’t handle anything from there. Therefore, if you want to customize something on the checkout page, please check with EDD’s support team or guides on customizing.
Regarding customizing emails, please reference our Themer’s Guide for both Event Tickets (email.php) and/or Event Tickets Plus (tickets.php)
Please also reference https://theeventscalendar.com/knowledgebase/hide-qr-code-from-event-emails/
And the code snippet from https://theeventscalendar.com/support/forums/topic/how-to-remove-youll-receive-your-tickets-in-another-email-in-events-tickets/#post-1087394 except replace “woo” with “edd” in all places.
Regarding the “Print Ticket” textual link that’s included in the purchase confirmation email, it would instead read “No downloadable files found.” without being linked to anywhere. It’s just the way EDD works, since there are downloadable files for each purchase. I’m guessing this isn’t what you’d want anyway.
Please let me know if you have any follow-up questions on this topic.
Hi, Alessio.
Thanks for your detailed request.
You could use some custom code to accomplish this by leveraging tribe_get_events() and querying by author.
If you need some coding help, you may want to ask your developer or reference our documentation and list of known customizers.
Please let me know how this goes for you.
Hi. Thanks for your question.
Please follow along with https://theeventscalendar.com/knowledgebase/using-qr-codes-event-tickets-plus/ and let me know if you have any remaining questions.
Hi, Jeff. I understand your feedback. That Zapier integration post is basically saying that Events are a custom post type and therefore you can trigger newly-published posts via Zapier.
Unfortunately, there isn’t more to it than that, such as triggering based on event date (as opposed to published date).
I believe you’re requesting the same thing as one of our existing feature requests: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/8391186-reminder-emails-for-x-days-before-event
Please do add your vote there.
This allows us to gauge interest in this particular feature request, which helps us prioritize our development efforts.
Please let me know if you have any follow-up questions on this topic.
Hi, Dave.
https://theeventscalendar.com/upcoming-changes-shopp-wp-ecommerce/ from June announced the end of Shopp being supported by Event Tickets Plus, which replaced all our standalone ticket plugins (WooTickets, ShoppTickets, etc) over a year ago.
Therefore, I’d suggest fully deleting the ShoppTickets plugin located at /hermes/walnaweb08a/b1689/pow.buffalomedianet/htdocs/hosted-sites/nyafp/wp-content/plugins/shopptickets/
From the snippet you shared, it looks like the only part that applies to Shopp is the last that starts with if (class_exists(‘TribeShoppTickets’)) {
Is that the only non-working part of your snippet?
Hi, Aein. Sorry you’re experiencing this.
Could you please share the link where I can see this happening on your site?
Hi, Julia. Thanks for posting here to let us know.
Could you please share the shortcode(s) you’re able to reproduce this issue with?
Phew! Glad we finally figured it out. The developer I asked to look at this is sharp!
I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.
For now, the recommended workaround is to have the single and archive slugs to not be the same.
I apologize for this issue and appreciate your understanding and patience.
Thanks for helping, @ybapubs!
Great suggestion.
Thanks for the screenshot.
Please understand that such in-depth customization help is not provided, per our Scope of Support / Terms.
From time-to-time, we are able to go a bit above-and-beyond to help out, and I’ll see what I can do for you.
If you need some coding help–now or in the future–you may want to ask your developer or reference our documentation and list of known customizers.
For your customization request, please confirm that you want a specific piece of text to be inserted by default whenever creating a new ticket (pre-fill the ticket’s Description) but if modified, use the modified version. Correct?
