[Victor]

Hi Barbara!

Thanks for getting in touch with us! I’d be happy to help you with this.

If you need to retrieve the next 3 upcoming events, you can use the following code:

$events = tribe_get_events( array(
'posts_per_page' => 3,
));

There’s no need to set a ‘start_date’ as it retrieves upcoming events by default. Let me share the following article as a reference > https://theeventscalendar.com/knowledgebase/using-tribe_get_events/

I hope that helps 🙂 Let me know if any follow up questions

Best,
Victor

[Victor]

Glad to know that Byron! 🙂

We’ll let you know about the fix once it is available for you to try.

Best,
Victor

[Victor]

Sure thing Suw! Thanks for following up with this.

We’ll let you know about updates on our side. For the moment, the snippet seems is a good workaround to this limitation.

Best,
Victor

[Victor]

Hi Travis,

There is no built-in functionality to create discounts that could be applied to tickets. However, if you choose to sell tickets using WooCommerce, you can create coupon codes to acomplish that. You can learn more about it in https://docs.woocommerce.com/document/coupon-management/

Were you able to solve the Buy Now button issue? Please let me know about it.

Thanks,
Victor

[Victor]

Hi Waldie!

I’m really sorry to hear you are having problems with our plugins. Let me help you with the troubleshoot so we can hopefully find the source of the problem.

The amount of tickets sold shows different on the different reports.

Could you please give us more information about this? Where do you exactly find the differences in the number of tickets sold? Can you share screenshots of the problem?

I can not get a Attendees list for the event

Are you seeing an error when navigating to the attendees page? Please also let us know more about this so we can understand more about the nature of the problem.

Additionally, please enable WP_DEBUG and WP_DEBUG_LOG. This will create a debug.log file inside the /wp-content directory.

After that, try reproducing the issues a few times, so that in case there is an error, it will be saved into the debug.log file. Please share that log file with us so we can see if any problem from there.

Thanks,
Victor

[Victor]

Hi Byron!

I’m sorry to hear you’ve been struggling with that issue. Let me help you with it.

The validation error you are getting is because you are using a .co.uk domain for the eventbrite import. Unfortunately, we are already aware of this issue so I will set this thread’s status to “Pending fix” and link it to the report. This way, we will notify you once a fix is released in one of our next maintenance releases of our plugins.

The workaround for the moment, is to modify the URL to use .com like the following:

https://www.eventbrite.com/d/united-kingdom--leeds/events--next-month/

Please try it out and see if it works for you.

We apologize for the inconvenience and we appreciate your patience while we work on this.

Best,
Victor

[Victor]

Hi Titus!

Thanks for getting in touch with us! Let me help you with that.

There is no built-in option to achieve that, so you’ll need to customize our template to make that happen. As a reference, I’d recommend our Themer’s Guide.

I’d suggest you take a look at the bar.php template file located at /wp-content/plugins/the-events-calendar/src/views/modules/

That is the template file used to show the find events button and datepicker, so you could remove that part of the code to make it happen.

I hope that helps 🙂 Let me know if any follow up questions.

Best,
Victor

[Victor]

Hi Cordes!

I’m sorry to hear you are struggling so much with that. Let me help you troubleshoot the issue so we can hopefully find the source of the problem.

As a first step, could you please share with us your system information by following this guide > https://theeventscalendar.com/knowledgebase/sharing-sys-info/ ? We’ll see if there is anything strange that would indicate an error from there.

Please share with us a link to the event you are having the problem with and also a screenshot of the ticket editor when on the Edit Event screen.

With all that information I will try to reproduce the same behavior on my end.

Thanks,
Victor

[Victor]

Hi Tim!

Thanks for taking the time to report this.

Unfortunately, what you are experiencing is an issue we are already aware of and it’s only happening when using the “Once” rule.

The good news is that our developers are already working on a fix.

As a workaround for the “Show details” not showing up, you can click the “Once” rule again to make it show up. I know that some users event found doing this would generate all the instances correctly, but it may not be the same for every situation.

I will set this thread’s status to “Pending fix” and link it to the report. This way, we will notify you once a fix is released in one of our next maintenance releases of our plugins.

We apologize for the inconvenience and we appreciate your patience while we work on this.

Best,
Victor

[Victor]

Happy to be of help 🙂

Glad to know is working fine on your end.

I’ll close this thread now, but feel free to open a new topic if anything comes up and we’ll be happy to help.

Best,
Victor

[Victor]

Hi Gesine!

Just wanted to let you know that we’ve just released a fix on our Event Aggregator server to address this issue.

There is no need to update anything on your end, but do make sure you are using the latest versions of The Events Calendar.

We apologize for the inconvenience and we appreciate your patience while we worked on this.

Please try your imports again and let us know if they work on your end.

Best,
Victor

[Victor]

Hi Xavier!

Just wanted to let you know that we’ve just released a fix on our Event Aggregator server to address this issue.

There is no need to update anything on your end, but do make sure you are using the latest versions of The Events Calendar.

We apologize for the inconvenience and we appreciate your patience while we worked on this.

Please try your imports again and let us know if they work on your end.

Best,
Victor

[Victor]

Hi Randy!

Just wanted to let you know that we’ve just released a fix on our Event Aggregator server to address this issue.

There is no need to update anything on your end, but do make sure you are using the latest versions of The Events Calendar.

We apologize for the inconvenience and we appreciate your patience while we worked on this.

Please try your imports again and let us know if they work on your end.

Best,
Victor

[Victor]

Thanks for the heads up Mathew!

Hey Suw, Mathew just made me realize his thread is private so you won’t be able to see the snippet he came up with as a workaround.

Let me share the following snippet Cliff created, which looks like a good workaround to having a different API keys with restrictions:

https://gist.github.com/cliffordp/a2ec320313afbc1ffb5f0e5ac654b7fb

As a reference, let me share with you a good article about best practices for implementing custom code snippets like this one > https://theeventscalendar.com/knowledgebase/implementing-custom-code-snippets/

Hope it helps. Let me know if any follow up questions.

Best,
Victor

[Victor]

Hi Agustin!

Thanks for getting in touch with us!

I’m sorry for a bit of delay in getting back to you. We are dealing with a high volume of threads at the moment and we are slowly getting back to normal response times.

Unfortunately, that is the default behavior when using Tribe Commerce tickets. You can’t purchase two ticket types at the same time, which is also why each ticket has its own “Buy Now” button.

If you want to allow multiple tickets per purchase, you can create WooCommerce tickets and sell tickets using WooCommerce checkout.

I hope that helps. Let me know if any follow up questions.

Best,
Victor

[Author]

Posts