Known Issues

Following recent changes to the Facebook API, a range of imports are no longer possible. If you experience difficulties importing from this source we recommend reading: https://theeventscalendar.com/knowledgebase/ea-fb-privacy-policy/

Registered users who submitted meta data with their purchase are not able to edit this data. Workaround: Make a template override of the orders-edit-meta.php template and use this one: https://gist.github.com/vicskf/8a6e772c839e3fcdcd8e84faac8589f7 ; You can find more info on template overrides in our Themer's Guide: https://theeventscalendar.com/knowledgebase/themers-guide/

When an event has a set shared capacity, but has no tickets that use shared capacity, then the available tickets number is wrong on list view and day view. To fix this open the Settings in the Tickets section and set the 'Shared Capacity' value to zero (0). Screenshot: https://cloudup.com/cSuPupVgX20

When using ET+ and Woo Subscriptions, renewals might fail giving a fatal error.

Adapative payments and NVP / SOAP apps more generally have been sunsetted by PayPal, seemingly effective as of 01 December 2017. Split payments should still work for existing users, but new users will not be able to take advantage of this feature for the time being. We are looking into different options to replace adaptive payments in our Community Tickets plugin.

With Event Tickets Plus 4.5.1 we have changed the wording of the setting "Hide attendees list on events page" and now it is called "Display attendees list". We felt that this is a more logical approach to the setting. However, a glitch happened during the implementation. For users who have updated to Event Tickets Plus 4.5.1, for events where the list was set to be hidden is now visible, and vice versa. To fix this with one shot you will need to run the below query directly in your database. This query will flip the Show/Hide attendees setting for all your events. Note, you might need to adjust the above queries if you are using a different table prefix than the default. And the query: `UPDATE wp_postmeta SET meta_value = IF ( meta_value <= 0, 1, 0 ) WHERE meta_key = '_tribe_hide_attendees_list';`

When exporting the CSV file for an attendee list it throws a PHP Warning. Also the following data columns are missing from the export: Ticket (number), Primary Information, Security Code, Check in. The workaround until the fix arrives is to roll back to Event Tickets 4.6 and Event Tickets Plus 4.6.

We have received several reports that events have disappeared from the month view after updating to the latest versions. We have already identified the source of this bug and are already working on a quick resolution. Until then the solution is to roll back (https://theeventscalendar.com/knowledgebase/downgrading-plugin-past-version/) to the previous versions: The Events Calendar 4.6.10.1 and Events Calendar Pro 4.4.22. Hang in there, the fix is on the way! Thanks for your patience and we apologize for the inconvenience!

We have received reports of ticket stock not decreasing with the ticket sales. If you are experiencing this, then please read the below article first before getting in touch with us. Thank you! https://theeventscalendar.com/knowledgebase/ticket-stock-doesnt-decrease/

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. URL 1: https://theeventscalendar.com/knowledgebase/daylight-saving-time/ ; URL 2: https://theeventscalendar.com/knowledgebase/time-zones/ ; We are also aware of a DST glitch when the Series Engine plugin is used / active when creating recurring events. If you are using this plugin, then deactivate it until you create a recurring event.

When recurring events, which expand to both summer and winter time, are created with the Series Engine plugin activated, then a 1 hour shift will occur in the event time before of after the DST date. To work around this, deactivate Series Engine until the recurring event is created. Note: deactivating the plugin will not influence already existing events. To fix existing events deactivate Series Engine and re-save the recurring event, check if the timings are correct on the front-end, then re-activate the plugin.