[Cliff]

Hi, Brian. You posted in our Pre-Sales forum from a user account that doesn’t have any purchases associated with it.

We don’t answer support questions for The Events Calendar core/free or Event Tickets core/free or their paid add-ons in the Pre-Sales forum.

If you made your purchase(s) through a different user account, please login to that account and then post in one of the paid forums.

Thank you for your understanding and thank you for using our plugins.

===

Possibly helpful references:

• Our free support forum for The Events Calendar (for bug reports and users helping each other — no usage support provided by us)
• You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

[Cliff]

Hi, Mario. Sorry you’re experiencing this.

Is the Eventbrite event Public? It’s required to be in order to use our Eventbrite Tickets add-on (a requirement of their API).

If it is already a Public event on Eventbrite.com, could you please provide the link to your Eventbrite event (the URL where it’s viewable on Eventbrite’s website)?

Also, are you experiencing this with other Eventbrite events on these 2 sites, or just this one Eventbrite event?

[Cliff]

Hi, Matthew. Thanks for your business; we appreciate it!

Please fill out our Refund Request Form and it should be processed within a day or two.

Thanks!

[Cliff]

Hi, David.

Both of those links require a password to view.

Regardless, my best guess is that the quantity available for that first link was 2, then you bought 2, then deleted the order, then you’re expecting the availability to go from zero back up to 2, but it doesn’t. Is this correct?

If not, please provide a screenshot of the first link’s ticket editing form from the wp-admin edit event screen so I can see the details of that ticket.

Thank you.

[Cliff]

Hi. Thanks for your detailed question.

What if you add a higher priority, like 100, to your add_action line, like in the code snippet in that other thread?

And may I ask why dequeuing ours and using your own (or the one from another plugin or your theme)?

Thanks.

[Cliff]

That’s the question… our plugin isn’t writing that output but maybe another one of your plugins is. Or maybe something in your server setup is doing so.

It could also be that you have @error_reporting( integer-here ); in your wp-config.php file. If you do, try changing that to zero or commenting out that line. Or it could be something in your php.ini file (which your web host would be able to investigate). Please reference https://secure.php.net/manual/en/function.error-reporting.php and let me know what you discover.

Thanks for your effort here.

[Cliff]

This reply is private.

[Cliff]

Thanks for that link.

The RSVP or paid tickets would be acquired/enrolled/purchased via each event’s single page. Therefore, I don’t believe there’s a way to do an “Enroll” link, unless “Details” goes to http://wpshindig.com/event/events-tickets-demo/ and “Enroll” just adds the hash so they’re taken further down that same page, like http://wpshindig.com/event/events-tickets-demo/#buy-tickets

Please let me know if this answers your question.

Thanks!

[Cliff]

Thanks for those screenshots.

This isn’t currently a known issue and your settings look correct (to not be displaying AM/PM, per https://codex.wordpress.org/Formatting_Date_and_Time) so I’d suggest following these recommended troubleshooting steps for your own site:

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• License Keys
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to Twenty Sixteen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you see while changing tickets quantity, navigating your site’s home page, events page, single-event pages, and any other of your site’s pages relevant to this ticket.

Then, please share your System Information (while in Testing for Conflicts Mode). That will give me a lot of extra information to help diagnose the problem.

You might also see if you can spot any console errors at your site. (If needed, you may reference our KB article Using Google Chrome Developer Tools.)

Let us know what you find out.

Thanks.

[Cliff]

Thanks for your understanding and detailed reply.

Please update me here if there’s more I can help with.

[Cliff]

Hi, Jake.

Thanks to other users reporting this same issue, 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.

I apologize for this issue and appreciate your understanding and patience.

The current workaround is to use a plugin like http://wordpress.org/plugins/delete-expired-transients/ (third-party, not guaranteed or supported by us)

[Cliff]

Hi, Marsha.

Thanks to other users reporting this same issue, 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.

I apologize for this issue and appreciate your understanding and patience.

The current workaround is to use a plugin like http://wordpress.org/plugins/delete-expired-transients/ (third-party, not guaranteed or supported by us)

[Cliff]

Hi, Steve.

Thanks to libo and a couple other users reporting this same issue, 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.

I apologize for this issue and appreciate your understanding and patience.

The current workaround is to use a plugin like http://wordpress.org/plugins/delete-expired-transients/ (third-party, not guaranteed or supported by us)

[Cliff]

Sure thing. Have a great one.

[Cliff]

Sounds good. Have a good day.

[Author]

Posts