Release: Events 3.0.2 / Events PRO 3.0.4 / Add-ons 3.0.1

[Rob]

While we still haven’t “officially” announced the 3.0 releases, many folks have seen the upgrade prompts and have initiated anyway. So this may be the hardest “soft launch” in the history of soft launches. But since the cat is out of the bag and we’ve released a couple small maintenance builds already, I did want to get a forum thread up here clearly outlining the specifics of what was released this morning.

Here’s what came out:

• The Events Calendar 3.0.2
• Events Calendar PRO 3.0.4
• WooCommerce Tickets 3.0.1
• Eventbrite Tickets 3.0.1
• Community Events 3.0.1
• Facebook Events 3.0.1

The Events Calendar 3.0.2

• Fixed bug with queries that included more than one post type. This should resolve issues with “Link to Existing Content” in the WordPress editor, attaching media to posts from the Media Library, and relationship fields in the Advanced Custom Fields plugin (thanks to users KARKS88 and ANDYWILMOT for catching this!)
• Fixed 404 in page title on month view when no events are in the month, and other 404-related tweaks (thanks to CYNTHIA, JOHN and ELLAEARTH for catching these)
• CSS files in the tribe-events directory of your theme are now loaded in addition to TEC css files, instead of replacing them
• Removed Select2 dependency in the Tribe Bar
• Fixed various issues with the Events List widget (thanks to DUVALDEMOCRATS and ZAVASTORONTO for the heads up)
• Tag permalinks are no longer malformed in tag cloud widget and single event pages (thanks to MARC for catching this)
• Addressed some previously non-translatable strings in the Tribe Bar
• Long event costs no longer overflow the designed box in list view
• Various minor bug fixes

Events Calendar PRO 3.0.4

• CSS files in the tribe-events directory of your theme are now loaded in addition to ECP css files, instead of replacing them
• Performance improvements to the plugin update engine
• Improved handling of international characters in iCal exports (thanks to PAUSSUS for catching this)
• Various bug fixes to the Events List and Events Calendar widgets
• Improved location search results (thanks to BISDIGITAL for getting the discussion going on this)
• Addressed some previously non-translatable strings in the Tribe Bar
• Various minor bug fixes

WooCommerce Tickets 3.0.1

• Fixed issue with ticket sales start and end date for some special date formats
• Updated template override path to use tribe-events folder
• Performance improvements to the plugin update engine

Eventbrite Tickets 3.0.1, Community Events 3.0.1, and Facebook Events 3.0.1

These releases contained no changes other than PUE / upgrade notification enhancements, to prevent unwanted/inaccurate update messaging when future updates are available.

—

Thanks to everyone for their support and patience as we ironed out this first batch of 3.0-centric bugs. If you find a bug wasn’t fixed that should be, or a new one has emerged upon updating, please create a new thread and we’ll do our best to help you out.

 

[Rob]

Folks: while I realize it’s going to make some people unhappy, for which I apologize in advance, I’ve deleted all the replies to this thread. It was indeed originally intended to be posted as CLOSED, so people could not reply and instead were required to create new threads for any issues they saw. Based on past experience, it just creates too much confusion to have multiple issues going in a thread this broad. As a matter of principle, please make sure to remember to log any issue as its own, distinct thread – so we can help get you a resolution in as timely a fashion as possible. Thanks for your understanding on this front.

That said, it does sound like a lot of the follow-ups reported here were related to the same issue. If you check this post (https://theeventscalendar.com/support/forums/topic/errors-on-all-event-pages/#post-56826) it should get you where you need to be as we patch this inconsistency.

If you’re still having problems after reviewing and taking the action noted in that thread, create a new ticket outlining your issue and what steps you’ve tried so far…and we’ll do what we can to help. Thanks to everyone for their patience and support!

[Author]

Posts