[Cliff]

Hi. Sorry you’re experiencing this.

Thanks for your detailed message.

Please install the Rewrite Rules Inspector plugin (third-party, not guaranteed or supported by us) and send me a screenshot of its analysis of https://wesleyanit.wpengine.com/event/pastor-appreciation-2017

[Cliff]

Got it via email. Thanks.

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. However, it seems it’s a simple fix.

If you want to try implementing it yourself, this is the proposed fix: https://github.com/moderntribe/event-tickets/pull/372/files

If you choose to try it, by editing /wp-content/plugins/event-tickets/src/views/tickets/email.php, please let me know if it worked for you.

[Cliff]

Hi. What you said makes sense. Could you please send a screenshot of each of these 2 imports’ settings/setup in a Private Reply?

[Cliff]

Sure thing, and thank you.

[Cliff]

Mark, I’m not totally clear what you’re asking, but anytime we get into users creating events (and editing the ones they created), that’s what Community Events is for. And if you want these users to also be able to sell tickets to their own events (and you can take a cut), then you’d need Community Tickets.

If this is what you’re wanting to get setup, please check out our Bundles for reduced pricing.

Again, we have a great refund policy.

Let me know if this answered all of your questions.

[Cliff]

Josen,

By default, /wp-content/plugins/the-events-calendar/src/views/single-event.php does pull the full size image via tribe_event_featured_image()

If you look at the top of of that PHP file, it tells you where to put the override file in your child theme… however, you wouldn’t need to do this because it already does what you want… so what’s likely happening is your Enfold theme’s override of single-event.php is changing this.

You can likely override this in your child theme (to override their override to set it back to our default, at least in this one respect), but if it doesn’t work how you expect, then please contact their support on this issue and let me know what you hear back from them.

[Cliff]

Hi, Stephan. Could you please create your own forum thread, linking to this one, and then also email a copy of a sample email to , linking to your new thread?

[Cliff]

Hi, Dennis.

It looks like your purchaser added a quantity of 2 tickets, completed checkout, and then what you’re seeing is what’s expected (same purchaser info but 2 different ticket IDs).

Please let me know if this lines up with what your user(s) likely did.

[Cliff]

Hi, Robert.

Your screenshot looks like this person changed the ticket quantity to 2, added to cart, and completed checkout. If this is what your purchaser actually did, then what you’re seeing is what is expected.

Please let me know if you have any follow-up questions on this topic.

[Cliff]

Hi, Richard.

Please reference https://theeventscalendar.com/knowledgebase/compatibility-with-woocommerce-extensions/ (basically that we cannot guarantee such things will work).

You could request this as a new feature (or maybe search to see if the idea was already posted by someone else) at our plugins’ UserVoice page.

This allows others who are interested in that feature to easily voice their support. We frequently review suggestions there to find out which ones are popular, then we implement as many of them as we can.

You might also try a workaround using the WooCommerce product pages for selling tickets. Here’s how to do that:
https://theeventscalendar.com/knowledgebase/selling-tickets-from-the-woocommerce-products-page/

[Cliff]

Hi, Matt.

I believe you’re requesting the same thing as one of our existing feature requests: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/15072414-could-we-get-event-tickets-to-work-with-wooextensi

Please reference the solution provided there and also add your vote.

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.

[Cliff]

Thanks for sharing, Felix!

We try to make our plugins extensible so you can accomplish such things just how you did! 🙂 There are hundreds of ways to customize and therefore not an option for every possible customization.

If there’s any question you had that I didn’t answer, please let me know and I’ll do my best to help.

[Cliff]

Hi, Mark.

Unless you want to develop something custom, you’d need to use our free/core Event Tickets‘ RSVP functionality (still considered a “ticket”) — or sell tickets via Event Tickets Plus (ET+) — and then ET+ could display “Who’s Attending”, like this: https://cl.ly/120v0z3v1a02

That would be a publicly-viewable list of attendees. However, there is a wp-admin list of event attendees that you’d be able to use for your own purposes (not publicly-viewable).

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.

[Cliff]

Hi, Jigna. Sorry, but I’m unclear what you’re trying to accomplish here. Please clarify exactly what you’re trying to do, and I’ll see how I can best be of help to you.

[Cliff]

Hi, Jennifer.

Sorry to hear about this. It’s not something I’ve heard of before, and obviously it’s a booger to try to replicate, debug, etc, as you already mentioned.

Could you provide any additional insight into some events that have their “wires crossed”, such as “purchasing a ticket for Event ID 7205 made Event ID 6028’s inventory go down instead of 7205’s”

Please also provide a screenshot of any/all ticket edit screen for applicable tickets (making sure we know which event each ticket belongs to).

I’d also highly recommend making sure your site isn’t generating any WP_DEBUG messages. Please enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages) and share any debug messages you see while trying to replicate this issue and doing other things on your site relevant to this ticket (such as visiting your site’s home page, events page, single-event pages, buying tickets, and anything else you can think to do).

Thanks for your effort here!

[Author]

Posts