[Cliff]

Hi, Kary. Sorry you’re experiencing this.

We do not provide support for using our plugin with W3TC, but we know many people do use it successfully.

http://tangerinemoons.com/using-wordpress-w3-total-cache-modern-tribes-event-calendar/ has also been a good reference for some of our users too. It may help you, but the site and content are not ours.

Please let me know how this goes for you.

[Cliff]

You bet!

FYI: I tweaked the snippet to work slightly better.

[Cliff]

You bet. Have a great rest of your week.

[Cliff]

Thanks for all those details. Please share a screenshot of where the Global Stock is set for this event’s tickets, and a screenshot of your Attendees Report table for this event.

Thank you.

[Cliff]

Try this:

https://gist.github.com/cliffordp/5899add4d18ccda7087534de6a04e52e

Please let me know how this goes for you.

[Cliff]

I’m glad we’re making progress.

You could reference the snippet at the bottom of https://theeventscalendar.com/knowledgebase/change-the-wording-of-any-bit-of-text-or-string/

You could also add something like this at the top of your own snippet to short circuit if not on the WooCommerce checkout page:

if ( ! is_checkout() ) {
return $translation;
}

If you don’t get things working just right, please provide your new full code snippet and I’ll take another look.

[Cliff]

Unfortunately, we couldn’t fit it into the latest update. I’d be hopeful that it’ll be fixed soon (weeks, not months) but I cannot guarantee that it’ll get prioritized in this fashion.

[Cliff]

Well that’s a bittersweet update… but I’m glad we’re no longer looking down a black hole of Safari issues.

The only confirmed (and therefore internally-logged) bug is for Filter Bar > Safari > Autocomplete field type loses placeholder text after using browser’s Back button

It wouldn’t be considered a bug of the highest priority because there is a workaround (use something other than Autocomplete field type) and another slight factor is because it only applies to one browser.

I’m stating this to be as open and honest as possible to set proper expectations. I’d expect it to be fixed eventually (weeks/months), but not soon (days/weeks).

If I had a quick fix for it, I’d share it now, but I don’t know where to start digging into this one.

Again, this thread should receive a reply once the applicable fix has been released. I apologize for this issue and appreciate your understanding and patience.

[Cliff]

That value is stored in the database’s postmeta table with the _unique_id meta_key

It gets created via get_next_ticket_number() method at Line 110 of /wp-content/plugins/event-tickets-plus/src/Tribe/Meta/Unique_ID.php

If you look at Line 118, you’re basically wanting $number = 0; to be filterable, such as defaulting to 1000 instead of 0, like this: https://cl.ly/0C0L241w041I

Is that correct?

If yes, each following sale is still going to be sequential; is that ok?

[Cliff]

Are you doing a Template Override or using an action hook to insert this button onto the Event Single page?

Please share your full code snippet, and I’ll see if I can help further.

[Cliff]

I’m glad to hear that! Thanks for the update.

[Cliff]

The src you copied is likely when you’re viewing in Gmail, so it looks like the actual file would be at http://localhost:8888/Ticket/wp-content/uploads/2017/03/qr_0273291a12af6e81f4a6ba3c5080b8a0.png

1. Does that file exist at that location? If not, do other files exist in your uploads directory that begin with “qr_”?
2. Do you have WordPress installed in a subdirectory called “Ticket”?
3. Are you buying an RSVP ticket or a WooCommerce ticket?
4. Please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you see while buying a ticket.

[Cliff]

Brandon, please utilize our Refund Request Form.

For reference, here’s another thread about this theme likely being the cause of the conflict: https://theeventscalendar.com/support/forums/topic/theme-clash/#dl_post-1231040

[Cliff]

Whatever you have in place now looks good: https://cl.ly/2l1S3i2A420R

If you don’t have a size between small and the next largest one, you could register a new size.

I personally like Simple Image Sizes plugin (third-party, not guaranteed or supported by us) to register a new size and also regenerate all image sizes.

You could also choose to use a different function instead of the one from our plugin. You could use get_the_post_thumbnail() which would generate srcset, which is probably best.

And/Or, you might be interested in a plugin like Force jpeg quality (again, third-party) if the issue is that your uploaded images are blurry but the original image on your computer wasn’t.

I hope this information helps. Please let me know how this goes for you.

[Cliff]

Hi, Tonn.

Where are the ticket numbers being publicly displayed that this would matter?

Also, I’m assuming you’re using WooCommerce, in which case, are you asking about the WooCommerce Order numbering?

If you share some annotated screenshots or video screen capture, it might help communicate what you’re seeing and what exactly the issue is.

[Author]

Posts