[Josh]

Hello csikimacko,

It’s been a while since we’ve heard from you. We like to close tickets after they’ve been inactive for a while. If you have any further questions, please don’t hesitate to open a new ticket.

Thanks!

[Josh]

Hello queenbee927,

It’s been a while since we’ve heard from you. We like to close tickets after they’ve been inactive for a while. If you have any further questions, please don’t hesitate to open a new ticket.

Thanks!

[Josh]

Hello Thomas,

It’s been a while since we’ve heard from you. We like to close tickets after they’ve been inactive for a while. If you have any further questions, please don’t hesitate to open a new ticket.

Thanks!

[Josh]

Hello motoshop,

It’s been a while since we’ve heard from you. We like to close tickets after they’ve been inactive for a while. If you have any further questions, please don’t hesitate to open a new ticket.

Thanks!

[Josh]

Hello Tony,

It’s been a while since we’ve heard from you. We like to close tickets after they’ve been inactive for a while. If you have any further questions, please don’t hesitate to open a new ticket.

Thanks!

[Josh]

Hello dbeedle,

It’s been a while since we’ve heard from you. We like to close tickets after they’ve been inactive for a while. If you have any further questions, please don’t hesitate to open a new ticket.

Thanks!

[Josh]

Hello jonschr,

Thanks for reaching out to us!

I took a loot at your site and noticed the issue that you’ve mentioned. I attempted to recreate the problem but was unable to do so on my local machine. Would you mind sending me an export of the events for your site so I can test with the same data you’re using?

Thanks!

[Josh]

Hello fenoco,

Thanks for reaching out to us!

We do have a tutorial that shows how to switch the ordering of the events to sort by post date for the main loop which may help with modifying your custom loop.

There is also some great information in this thread that may also help. It uses pre_get_posts() to set the orderby parameter.

I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Josh]

Hello 360zen,

Thanks for reaching out to us!

That is definitely a strange issue to be having. I took a look at the site and it looks like you can get that section cleared up by adding a clear:both; style to the .tribe-events-list-separator-month element. This can be added directly to your theme’s (or child theme’s) stylesheet.

Let me know if you have any further questions.

Thanks!

[Josh]

Hello thestudiodoor,

Thanks for reaching out to us!

You’re correct that our ticketing plugins are not fully compatible with recurring events at this time. Unfortunately, since this will be a relatively complex integration, there isn’t a direct work around at the moment. If you would like, you can vote for this feature on our UserVoice page.

Currently, when creating tickets for recurring events, the single ticket will be used across all recurrences of this event. This can probably be best understood when thinking about their quantities. Let’s say you have a recurring event with 5 tickets available for the event. If a ticket is sold, there is now only 4 available for every subsequent event ( rather than 5 available for each recurrence of the event ).

Hopefully I was able to answer your question. If you have any further concerns please don’t hesitate to ask.

Thanks!

[Josh]

Hello dejavudotcom,

Thanks for following up with us!

Sorry for the confusion on the version numbers. Looks like we’re both looking at the same file now :).

On closer inspection, I noticed that although the filter provides a result, the results I was getting weren’t accurate. It looks like this is possibly due to the query expecting an array which isn’t output when the “select” type is used. Consequently, implementing a select option for that field will be a little more complicated than I initially suspected.

You could potentially use the TribeEventsFilter_Category.php along with the tribe-filter.class.php to figure out the best way to implement the select for the venue filter. You could also suggest this as a feature for our developers to consider for a future release on our UserVoice page.

I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Josh]

Hello mtmuddnadd,

Thanks for reaching out to us!

I tested out your scenario on my local install and was able to replicate the issue that you’re noticing. I’ll create a bug report and have our developers look at the issue.

Until then, I was able to get the setup you’re looking for by working backwards with the tickets. So, if you delete the tickets in there now and start by adding the second 25% off discount tickets first, you should be able to add the earlier 30% discount tickets after that.

I’m sorry for any inconvenience this issue has caused but hopefully this work around will work for you until we’re able to get the issue resolved.

Thanks!

[Josh]

Hello zobel,

Thanks for reaching out to us!

Unfortunately there isn’t a single button click to cancel event and have users refunded and notified at the same time. There is a UserVoice page for this feature that you can vote on for our developers to consider for an upcoming release.

In the meantime, you could export the list of attendees and then upload their emails to an email blast service such as Mailchimp. You could then send out a notification en masse to all registrants. Refunds could also then be managed via the WooCommerce -> Orders section of your WordPress dashboard.

I’m sorry for the inconvenience but hopefully this will help to get you pointed in the right direction.

Thanks!

[Josh]

Hello breaktheseal,

Thanks for reaching out to us!

Each individual event requires it’s own unique identifier and subsequently gets it’s own page based on the date of recurrence. Unfortunately, I don’t believe there is a straightforward way to get the slug modified for all events without the date of the event.

Could you give me more detail on what you’re trying to accomplish? Maybe we can find a solution that will fit your needs.

Thanks!

– Josh

[Josh]

Hello eventiintoscana,

Thanks for reaching out to us!

Unfortunately this is the way the datepicker currently works on mobile. There are some work arounds that will require some minor custom development work. Here are some solutions others have used to solve this same problem you’re experiencing.

You could also submit a request on our UserVoice page for our developers to consider this feature in an upcoming update to the plugin.

I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Author]

Posts