[Cliff]

Hi, Dan.

The issue here is that your iCal file does not adhere to the Unique Identifier (UID) property from the iCalendar specification.

Here are the logistics of the issue:

• Let’s say you have “Event A” in the .ics file that your iCal URL downloads.
• The first time I download the .ics file, “Event A” might have the UID of 54822a76.
• Then, if I immediately re-download the .ics file a second time, “Event A” no longer has that same 54822a76 UID. Instead, it has a completely different one.
• Because Event Aggregator stores each imported event’s UID (specifically for the purpose of detecting event updates and avoiding duplicate events), it does not (and cannot) know that the 2nd dowload of “Event A” is the same “Event A” from the 1st download of this iCal URL.

This issue isn’t common, but we do see it from time-to-time. It’s usually an issue with iCal feeds from custom software, but it’s not an issue with major calendar providers like Google Calendar.

Therefore, the only resolution for this would be to discuss the situation with the source/author of that iCal URL and ask them to follow the iCalendar spec, specifically for the UID property.

Please let Victor know if you have any follow-up questions on this topic.

[Cliff]

Hi, Kevin.

The issue here is that your iCal file does not adhere to the Unique Identifier (UID) property from the iCalendar specification.

Here are the logistics of the issue:

• Let’s say you have “Event A” in the .ics file that your iCal URL downloads.
• The first time I download the .ics file, “Event A” might have the UID of 54822a76.
• Then, if I immediately re-download the .ics file a second time, “Event A” no longer has that same 54822a76 UID. Instead, it has a completely different one.
• Because Event Aggregator stores each imported event’s UID (specifically for the purpose of detecting event updates and avoiding duplicate events), it does not (and cannot) know that the 2nd dowload of “Event A” is the same “Event A” from the 1st download of this iCal URL.

This issue isn’t common, but we do see it from time-to-time. It’s usually an issue with iCal feeds from custom software, but it’s not an issue with major calendar providers like Google Calendar.

Therefore, the only resolution for this would be to discuss the situation with the source/author of that iCal URL and ask them to follow the iCalendar spec, specifically for the UID property.

Please let me know if you have any follow-up questions on this topic.

[Cliff]

Hi, Sebastián.

Sorry you’re experiencing this issue.

The wp-admin Attendee Report screen can sometimes suffer such performance issues when there are many tickets/attendees for a single event, and our developers have it scheduled to be improved in an upcoming release (likely a couple months at the earliest, and we don’t give ETAs).

This thread should receive a reply once the applicable update has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands.

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

Please let me know if you have any follow-up questions on this topic.

[Cliff]

Hi, Yuval.

Anytime you start using our Themer’s Guide, we can’t really advise what CSS selectors you’d need to use because you might have altered them.

Therefore, after you have your template how you want it, please try a plugin like SiteOrigin CSS because it helps you visually build CSS selectors via its Inspector and Visual Editor, which I’d guess would be helpful to you.

If you’re not a CSS expert, Jetpack’s Custom Design reference may prove helpful.

Please let me know how it goes for you. If you don’t find joy with this, please send me a link to view this on your site and also send an annotated screenshot of what changes you’d like to see.

[Cliff]

Hi, Scott.

If you’re not using a plugin like Yoast SEO that does this for you, you could do something like this:

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

Of course, customizing it for your own needs.

Please let me know if you have any follow-up questions on this topic.

[Cliff]

Hi, Naim. Thanks for your interest in our plugin suite.

So you enter data in your app, which triggers your Zapier Zap to create a Google Calendar entry. When you modify an event/date/time in your app, the Zapier Zap doesn’t update the Google Calendar entry? I’m surprised to hear that (this might be related).

If you choose to continue using Google Calendar, our Event Aggregator (EA) solution can pull in from it. However, it’s not a two-way sync if you modify the imported event in WordPress.

If you are looking to get away from Google Calendar, you could sign up for EA to migrate your old data over but then not renew it after you’re done using it. Going forward, you can use our free/core The Events Calendar plugin without the need to purchase any other add-ons. We don’t place limits on how many events you can have or anything like that.

For your WP app, you could reference https://github.com/moderntribe/the-events-calendar/blob/master/src/Tribe/API.php instead of needing to do anything with Zapier.

Please let me know if you have any follow-up questions on this topic.

[Cliff]

Hi, Big Fish.

Just checking back here to see if you got my previous message asking if the bug is still outstanding.

Our developers are standing by awaiting your report.

Thank you.

[Cliff]

I understand.

Please create a test EDD product and test this checkout/cancelation scenario with a non-ticket product.

Thank you for your effort here.

[Cliff]

Hi, Nicolas.

This plugin .zip can be installed to your WordPress site as a new plugin: https://cl.ly/3s3k2x2T1g21

Please try it out on a sample ticket (ideally a separate staging/development install) and let me know if it works for you.

If you have any follow-up questions or feedback, please include annotated screenshots, screen capture video(s), and/or relevant URLs to clarify exactly what’s happening.

Please let me know how this goes for you.

[Cliff]

Jake, since you inquired about this thread from your other thread, I wanted to let you know that I pinged our development team for an update on this one.

I’ll let you know what I hear from them.

[Cliff]

Hi, Ron.

Please check out this code snippet:

https://gist.github.com/elimn/36b24ada494337b5dad7

Please let me know how this goes for you.

[Cliff]

Hi, Bobby. There’s a recently-discovered bug that was introduced in Eventbrite Tickets version 4.4.7 that causes none of the Eventbrite tickets to display. So, assuming you have permission to import an event from Eventbrite, the tickets would be showing right now anyway!

I’ve reported it to our developers and expect a fix to be released sometime soon.

If you’d like to fix it yourself right away, please add an exclamation point between || and in_array at Line 1153 of /wp-content/plugins/the-events-calendar-eventbrite-tickets/src/Tribe/API.php

Of course, we always recommend restorable database and file backups before modifying anything on your site.

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.

[Cliff]

Sorry for the multiple replies but I actually did confirm this bug!

I’ve reported it to our developers and expect a fix to be released sometime soon.

If you’d like to fix it yourself right away, please add an exclamation point between || and in_array at Line 1153 of /wp-content/plugins/the-events-calendar-eventbrite-tickets/src/Tribe/API.php

Of course, we always recommend restorable database and file backups before modifying anything on your site.

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.

[Cliff]

Sorry for the multiple replies but I actually did confirm this bug!

I’ve reported it to our developers and expect a fix to be released sometime soon.

If you’d like to fix it yourself right away, please add an exclamation point between || and in_array at Line 1153 of /wp-content/plugins/the-events-calendar-eventbrite-tickets/src/Tribe/API.php

Of course, we always recommend restorable database and file backups before modifying anything on your site.

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.

[Cliff]

Hi. Sorry you’re experiencing this bug that was introduced in Eventbrite Tickets version 4.4.7

I’ve reported it to our developers and expect a fix to be released sometime soon.

If you’d like to fix it yourself right away, please add an exclamation point between || and in_array at Line 1153 of /wp-content/plugins/the-events-calendar-eventbrite-tickets/src/Tribe/API.php

Of course, we always recommend restorable database and file backups before modifying anything on your site.

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.

[Author]

Posts