[Josh]

Hey Lisa,

To clarify, when purging events, is the intention to delete all events and re-import some of those same events?

Thanks!

[Josh]

Hey Ben,

The core issue is that users could be checked in via the QR code once they had already been “checked in” (either manually by clicked the buttons within the attendee list or by having the QR code scanned which is the issue you’re currently facing).

Once this issue is addressed both sides of the issue resolved and you’ll be notified here once it is ready to be released.

Hopefully this helps to clarify some of the confusion I may have introduced with the previous response.

Let me know if you have any further questions.

Thanks!

[Josh]

Hey,

It’s been a while since we’ve heard from you.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey,

No problem! Happy to help.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Smith,

If the site is public, you can send me a link to the event or the link from the generated Google Calendar button. If not, you can send me the iCal export file and I can manually import into Google. The second may not be as helpful but may still import with the same issue into Google.

Thanks!

[Josh]

Hey Shannon,

Awesome! So the events are now showing with the proper URL structure and linking correctly for you? Same thing for newly created recurring events?

Thanks!

 

[Josh]

Hey Buddy,

Awesome! Happy to help.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey Lisa,

Thanks for following up with us!

I did some further testing and was still able to initially see and import the events again. However, after going through and deleting all of my events and emptying the trashed events, I’m now seeing the issue you’re describing.

If I now try to import the same file (the already uploaded and then re-uploaded) no matter what parameters I set it doesn’t recognize any events in the file. Let me do some further testing to see if there is anything else I can come up with or what the particular bug might be here.

Thanks!

[Josh]

Hey Matthew,

Thanks for following up with us!

The first thing to check if the code isn’t showing is to verify that the file is in the correct folder structure within your theme and matches where it was in the plugin. Do you mind typing out the folder structure that is currently used for the snippet?

For each of the other views, they have their own “single-event.php” file within their associated folders. You can wrap the entire display portions of those with the same “tribe_event_is_multiday()” conditional from the above snippet.

Let me know if this helps.

Thanks!

[Josh]

Hey Keith,

I believe this brings us back to the original comment. No doubt there is definitely some confusion here that needs to be addressed on our side with how the plugin works in this regard.

However, currently even if an attendee is deleted from the attendee list they are still associated with a completed/paid purchase within WooCommerce. The best option for keeping everything consistent right now would be to “refund” tickets via the associated WooCommerce order rather than deleting them from the list.

Thanks!

[Josh]

Hey,

It appears that the original response was marked as correct.

I’ll go ahead and close this thread for now. If you have any further questions, please don’t hesitate to open a new one.

Thanks!

[Josh]

Hey,

I apologize for the confusion. You can filter that information by utilizing the “tribe_events_event_schedule_details_formatting” filter. You can see how that section is built and determine what you would like to filter out by reviewing the “tribe_events_event_schedule_details” function you mentioned above.

Let me know if this helps.

Thanks!

[Josh]

Hey Hugues,

Thanks for reaching out to us!

I apologize for the inconvenience of this issue. It does appear to be something that our internal team has reported with the latest release and something that we’ll addressing shortly.

I’ve added this thread to our internal ticket for tracking this bug and you’ll be notified here as we make progress.

Let me know if you have any questions or concerns about the process.

Thanks!

[Josh]

Hey Jessica,

Thanks for reaching out to us!

Unfortunately, there isn’t support for this type of use of our ticketing solutions with recurring events. What you’re seeing in not knowing which instance the ticket is for is due to the limitation. Tickets are only available for the event as a whole and not each individual event.

I apologize for any confusion there may have been when purchasing. We do try to make the warning clear and have a note on this in the “What does it do” section of the page here however we do understand that there can sometimes be an automatic expectation for the tickets to work this way. This is something that we are currently working on.

If you have any further questions, please don’t hesitate to ask.

Thanks!

[Josh]

Hey Peter,

Thanks for reaching out to us!

Would you mind giving a little more detail about the error that you’re seeing? Is it that only the first instance of a recurring event is displaying on your calendar? Any additional details will help us in trying to diagnose or determine what is going on here.

Thanks!

[Author]

Posts