Known Issues

Description:

Some users are experiencing an issue where editing an event date or time in the classic editor caused the event to revert to the current date and time.

Workaround:

• Go to Events > Settings > Display and change the Compact Date Format to the default (YYYY-MM-DD).
• Use the block editor for editing events.

Affected Products:

The Events Calendar, Events Calendar Pro

Internal Ref.:

ECP-1352

Description:

FSE themes are now alive and kicking. In fact, starting with WordPress 6.0, the default theme, TwentyTwentyTwo, is an FSE theme.

For now, FSE themes don’t break with The Events Calendar, but there is still significant work to be done on our end to provide support for basic things such as:

• Template overrides
• Programmatical customizations
• Legacy Widget support
• Etc…

As you can imagine, we are not happy about this and we’ll spend the rest of the year gradually improving FSE support. Hang in there!

Workaround:

• Temporarily use a non-FSE theme

Affected Products:

The Events Calendar

Internal Ref.:

TEC-4419

Description:

Some of our customers using Event Aggregator and Eventbrite Tickets are experiencing connection issues to their Eventbrite accounts.

This can manifest in a number of ways:

• Event created in The Events Calendar not created on Eventbrite
• Import jobs not being processed
• Getting a “There has been a critical error on this website.” message while connecting to the Eventbrite account

TL;DR we are actively working on stabilizing the connection to the Eventbrite API. Hang in there!

Workaround:

Refresh connection / Try connecting again a bit later

Affected Products:

Event Aggregator, Eventbrite Tickets

Internal Ref.:

EA-441

Description:

Some sites are hitting errors when trying to migrate to the new event data storage system launched in The Events Calendar 6.0.

Known fixed errors:

• The [number] is greater than the duration of the event
• [Event model does not have an RSET: it should at this stage.]
• [The start_date and start_date_utc has a conflict when using the timezone of the event.. The end_date_utc does not match the value of end_date with the timezone.]
• [The provided timezone is not a valid timezone.]
• [The start_date should be a valid date.. The provided timezone is not a valid timezone.. The start_date_utc requires a value.]
• [No occurrences created.]
• [Invalid period in RDATE: start date must must be before end date.]
• [Undefined index: same-time]
• [Duration must be a positive integer. The end_date_utc does not match the value of end_date with the timezone.]
• [Attempting to run Single Event strategy for recurring event. Is a strategy missing for this type of event?]

Workaround:

Many of the above errors can be avoided or fixed by following the Troubleshooting steps in the Knowledgebase.

Another option is to simply refrain from migrating your site. You can still continue to use all the pre-6.0 features and functionality.

Affected Products:

The Events Calendar, Events Calendar Pro

Internal Ref.:

ECP-1304 and related

Description:

Some users have reported the following error after updating to Events Calendar Pro 6.0:

Fatal error: Declaration of Tribe__Events__Pro__Mini_Calendar_Widget::__construct() must be compatible with Tribe\Widget\Widget_Interface::__construct($id_base = '', $name = '', $widget_options = Array, $control_options = Array) in /home/sites/6b/8/82013eb231/public_html/wp-content/plugins/events-calendar-pro/src/deprecated/Tribe__Events__Pro__Mini_Calendar_Widget.php on line 9

Workaround:

Temporarily roll back to The Events Calendar 5.16.4 and Events Calendar Pro 5.14.5

Affected Products:

Events Calendar Pro

Internal Ref.:

ECP-1317

Description:

A subset of users experienced errors on their site when updating to The Events Calendar 6.0. This was happening when calling tribe_context( )->is( is_main_query ) too early in the execution.

Workaround:

Affected Products:

The Events Calendar

Internal Ref.:

TEC-4464

Description:

The Events Calendar site owners that are using Skeleton Styles (under Events > Settings > Display) are seeing huge SVG icons on the single event page after updating to 5.16.0+

Workaround:

• Don’t use Skeleton Styles until the fix is released
• Use CSS to reduce the size of the icons: svg.tribe-common-c-svgicon–cal-export (!important might be required)
• Use CSS to hide the icons: tribe-common .tribe-common-c-svgicon

Affected Products:

The Events Calendar

Internal Ref.:

TEC-4399

Description:

When creating a new event, then the event time zone is set to UTC+0 regardless of the WordPress time zone setting under Settings > General and regardless of the TEC time zone settings under Events > Settings > General tab.

This is a known issue when using the Avada theme. This is not something we can fix on our end, it will have to be a fix from Theme Fusion / Avada. They already know about the issue, and they are planning to include the fix in their next update.

Workaround:

Reverting to the previous version of Avada should solve the issue.

Affected Products:

The Events Calendar

Internal Ref.:

n/a

Description:

This issue impacts users of the Classic Editor plugin that have set the Allow users to switch editors option to Yes and the default editor for all users to Classic Editor.

Under these conditions, when trying to create or edit an event in the Classic Editor, the Events Calendar meta boxes do not load.

As a result, it’s not possible to edit or see the date/time, organizer, etc

This issue is particularly noticeable for users that are also using a page builder (Divi, Avada, Elementor, Beaver, etc.).

Workaround:

Head over to Events > Settings > General and uncheck the Enable Block Editor for events settings and hit Save Changes.

In the text of the Classic Editor, remove the block code (e.g. <!–) and save the event. (https://d.pr/i/jUUc07).

Affected Products:

The Events Calendar

Internal Ref.:

TEC-4287

Description:

For some users, when trying to import an Events CSV file, all seems to be working fine.

But, upon closer examination, there appears to be missing information from the import: events, category assignment, featured image, etc. Exactly as though some records were skipped.

The issue seems to be related to the configuration of the webserver for some users. There were some reports of CSV imports taking a really long time and even timing out.

Workaround:

In most cases, staying on the screen (as opposed to navigating away, fixes the issue). Some users have also reported fixing the issue by running the same import several times until completion. Others were not so lucky.

Affected Products:

The Events Calendar

Internal Ref.:

TEC-4079

Description:

Event Tickets Plus App doesn’t work with Tickets Commerce tickets.

Affected Products:

Event Tickets Plus App, Event Tickets, Event Tickets Plus

Internal Ref.:

ET-1436

Description:

Event Tickets Plus App showing “Ticket scanned already” message for unscanned tickets.

Affected Products:

Event Tickets Plus App

Internal Ref.:

ETPAPP-14

Description:

When a ticket is created with Tickets Commerce (Event Tickets), that event will not sync into Promoter.

The fix will be included in the next version of Event Tickets, which is planned for the first half of April.

Workaround:

Download and install this development version of Event Tickets.

Affected Products:

Event Tickets

Internal Ref.:

ET-1458

Description:

Adding venues while creating events works great.

However, in the following cases, the state/province disappears (field is blank after saving and nothing gets displayed on the FE) when the address is not US-based:

1. Creating the Venue via the Venue UI
2. Editing an existing Venue

Workaround:

Download the following temporary version of The Events Calendar and replace your current one until the fix is released

Affected Products:

The Events Calendar

Internal Ref.:

TEC-4309

Description:

When a new attendee is generated for a “Tickets Commerce” ticket, then the attendee does not get pushed to Promoter.

Workaround:

There is no known workaround at the moment.

Affected Products:

Event Tickets

Internal Ref.:

ET-1475

Description:

Subscribing to Google Calendar imports events beginning from the 1st of the month, including past events. This also affects the count towards the event import limit (30 by default).

For example, if you visit your site’s /events page on March 14th and click on Subscribe To Calendar > Google Calendar, the events imported will start on March 1st.

Workaround:

None. Wait for the upcoming The Events Calendar release.

Affected Products:

The Events Calendar

Internal Ref.:

TEC-4223

Description:

Since the WooCommerce v6.3.0 update, the attendee registration page is not working anymore for WooCommerce Tickets.

Workaround:

Using the following snippet: https://gist.github.com/rafsuntaskin/eddc2b73b3750a6a03db35f482b011d4

Affected Products:

Event Tickets Plus

Internal Ref.:

ETP-785

Description:

For some users, it is not possible to complete checkout while trying to sell tickets via Tickets Commerce. They see JavaScript errors in their console and possibly the following errors when they are trying to pay:

• “Cannot read properties of undefined (reading ‘post’)”

Workaround:

Update to Event Tickets 5.3.1

Affected Products:

Event Tickets

Internal Ref.:

ET-1447

Description:

For some users that are using only Event Tickets without Event Tickets Plus, the version 1 of the tickets block may be rendered and not the version 2 where we fixed many issues with total calculation for currencies like euros.

As a result, they may be experiencing incorrect total preview when they add tickets.

Workaround:

Update to Event Tickets 5.3.1

Affected Products:

Event Tickets

Internal Ref.:

ET-1448

Description:

If the user has a custom Attendee Registration page that uses the same slug as the “Attendee Registration URL slug“, When the user navigates to the frontend of the attendee registration page, then it will always render the content using the “Default Page Template“ instead of the one specified for the Custom Page.

Affected Products:

Event Tickets Plus

Internal Ref.:

ETP-784

Description:

In really late February 2022, Fremius found a severe security vulnerability in its library.

This monetization, analytics, and marketing library for WordPress is used by more than 400 of the most popular WordPress plugins, including The Events Calendar, Event Tickets.

Upon being notified, we upgraded the Freemius found in our plugins to version 2.4.3 within 24 hours.

This completely patches the vulnerability.

Workaround:

Upgrade to The Events Calendar 5.14.0.4 + and Event Tickets 5.3.0.1 +.

Affected Products:

The Events Calendar, Event Tickets

Internal Ref.:

Description:

When creating a new organizer or venue at the backend, the section where you enter the specific information about the organizer/venue like address, email, phone number and so, is missing.

They only appear after you save for the first time.

Workaround:

Upgrade to The Events Calendar 5.14.0.3 +

Affected Products:

The Events Calendar

Internal Ref.:

Description:

Google has recently leveled up in regards to the information it is expecting from an event. This is why we added an event status option dropdown as of The Events Calendar 5.11.0.

This setting will keep Google happy with any new event that you create.

Alas, the event status option is not retroactive. In other words, if you created events before the feature was released, they will not have a defined event status.

Of course, you could manually go into each event and define an event status. But that is pretty time-consuming. We have a better solution 🙂

Workaround:

Use the following snippet to add the eventScheduled event status to all events where an event status was not added.

Affected Products:

The Events Calendar, The Events Calendar Pro, Virtual Events

Internal Ref.:

Description:

Whenever the Calendar is set as the home page of a site, the default mobile view setting is not respected when looking at the site on a mobile device.

Workaround:

Upgrade to the latest version of The Events Calendar

Affected Products:

The Events Calendar 5.1.2

Internal Ref.:

TEC-3826

PHP 8.0:

Our plugins support PHP 8.0, although it is possible to still run into some errors when using PHP 8.0. Once these errors are reported to us we will log a bug ticket and a fix will be worked on as soon as possible.

Fatal errors on PHP 8.0 are likely to be treated as priority bugs.

Keep in mind, that at the time of writing, PHP 8 is still in “beta” for WordPress.

PHP 8.1:

PHP 8.1 is very recent. It was officially released on November 25th, 2021, and WordPress itself doesn’t yet fully support it.

We haven’t tested or developed anything for PHP 8.1 and thus, our plugins are not yet compatible with it. The development team will be working on supporting PHP 8.1, but right now there’s no defined timeline for this.

If you encounter any errors you can report them to us. We will log a bug ticket for it, which will be really helpful for us when we start working on PHP 8.1 compatibility.

Affected Products:

All

Internal Ref.:

n/a

Description:

After updating to The Events Calendar 5.11.0, logging into the WordPress dashboard, and visiting the events listing page, all of the events have the same title.

This issue seems to happen when:

• Using object cache with Redis from LiteSpeed Cache
• Using object cache with Redis Object Cache standalone plugin
• Using Memcached in LiteSpeed

Workaround:

The following two workarounds are known until we fix this:

• Disable object caching
• Downgrade to The Events Calendar 5.10.1

Affected Products:

The Events Calendar 5.11.0

Internal Ref.:

BTRIA-1072

Description:

After updating to Event Tickets Plus 5.2.9, when visiting an event page that has a ticket, then there is either a fatal error on the page or the ticket form is empty.

This error comes from a conflict with some WooCommerce payment plugins.

Workaround:

Until a more permanent fix is released you can use the following snippet to fix the issue. Copy the snippet into your (child) theme’s functions.php file.

• https://gist.github.com/rafsuntaskin/94c0463f2390ee0a106a14c304c3e7bc

Affected Products:

• Event Tickets 5.1.9
• Event Tickets Plus 5.2.9

Internal Ref.:

ET-1174

Description:

When trying to update Event Tickets Plus to version 5.2.9, the system would give the following error, even with active licenses:

503 ( Expired License Key ): Sorry, your access to this file has expired.

This was a tagging glitch in our latest release of Event Tickets and Event Tickets Plus, which has already been fixed.

The current versions are:

• Event Tickets 5.1.9
• Event Tickets Plus 5.2.9.

The update should work now seamlessly. If you are still having issues with the auto-update, please, log in to your account at theeventscalendar.com, go to Downloads, select the right versions from the dropdowns and proceed with a manual install.

Affected Products:

Event Tickets Plus

Internal Ref.:

n/a

Description:

When using the updated design for The Events Calendar (Events > Settings > Display tab > Use updated calendar design) and clicking on an event to look at the details the actual calendar page reloads and the single event page does not load.

So far we have heard of this case when using any of the following:

• ListingPro theme
• Winwood theme
• PDF Poster plugin

Workaround:

Until the issue gets resolved downloading and installing this plugin could help solve the issue.

If the above plugin doesn’t help or if you have experienced the same issue with a different theme or plugin, please let us know about it.

Affected Products:

The Events Calendar

Internal Ref.:

TEC-3975

Description:

When using the Avada theme, if there are multiple events on a day, then the events might overflow the day cell in month view. Example screenshot.

The issue is coming from the theme, the developers have already been notified.

Workaround:

Until the issue gets resolved the following CSS snippet should fix this glitch:

.tribe-events-view--month .tribe-events-calendar-month__day {
    height: auto;
}

Affected Products:

The Events Calendar 5.x.x

Internal Ref.:

n/a

Description:

Daylight Saving Time can confuse the best of us. If your recurring events appear to be offset by an hour and you’re note sure why, check out these knowledgebase articles to learn how your events may have been affected.

• Dealing with Daylight Savings
• Working with Time Zones

We are also aware of glitches that can happen when the Series Engine plugin is active. If you are using this plugin, please note that they have settings you can take advantage of to resolve this problem.

Workaround:

n/a

Affected Products:

Events Calendar Pro

Internal Ref.:

n/a