Events Calendar Pro
Fixes
- Display recurrence section in classic editor for all users that don't have blocks
Tweaks
- Ensure that recurrence rule types use their plural form when appropriate in the Events block
Features
- Added new recurring event marker element for Event Date Time block
Tweaks
- Improved default yearly recurrence rule options to be more intuitive
Fixes
- Adjusted recurrence options in the Event Date Time block to prevent confusion with overlapping elements
- Updated the code responsible for generating recurring event tooltips so it does not interfere with the result of calls to tribe_events_template_data()
- Set fallback to default timezone if event timezone is not valid for Countdown Widget
- Corrected an issue where a single instance of a recurring events redirected to the series /all page
Features
- Added recurring events support to the Events Date Time block
- Added default content support to the Organizer and Venue blocks
- Any configured Additional Field now has a corresponding block in the block editor
- Added option to Additional Fields settings to include configured fields blocks on new events by default
Tweaks
- Exclusion rules are now called exceptions when configuring recurring events in the block editor
- Changed views:
blocks/additional-fields/checkbox,blocks/additional-fields/dropdown,blocks/additional-fields/radio,blocks/additional-fields/text,blocks/additional-fields/textarea,blocks/additional-fields/url
Fixes
- Style regression for series end element with gutenberg style override
Languages
- 2 new strings added, 50 updated, 0 fuzzied, and 0 obsoleted
Features
- Add filter
tribe_events_pro_show_recurrence_meta_boxto control the render of the recurrence meta box
Fixes
- Fixed some HTML in the recurrence-building section of the event editor so it's valid and doesn't create issues with other HTML on the page
- Fixed the setting-up of strings in the Tribe Bar datepicker to ensure they're translatable into languages other than English
Tweaks
- Prevent certain geolocation-related prompts from showing if The Events Calendar's built-in Google Maps API key is being used
Features
- Add two new filters to extend custom fields markup:
tribe_events_pro_before_custom_field_contentandtribe_events_pro_after_custom_field_content
Fixes
- Fixed a JavaScript error that would occasionally arise when using the "Near:" search input in the Tribe Bar on non-Map views
- List only enabled views on the "Default mobile view" option. Thanks to wescole, John Meuse and others for reporting!
Tweaks
- Ensure calls to the Google Maps Geocoding API are not made unless an API key supporting that is present
- Make sure Geolocation search features are only accessible and visible when a Google API key that supports those features is present
- Added
tribe_events_pro_geocode_addressesfilter to allow for disabling of Google Maps API geocoding using Google Maps API key
Languages
- 26 new strings added, 175 updated, 0 fuzzied, and 25 obsoleted
Fixes
- Prevent broken and low-resolution Google Maps if user has not provided a Google Maps API key of their own by providing our own fallback API key
- Prevent duplicate events from being created on the first date of a series, thanks to Mathew for the detailed instructions to reproduce
- Only load widget assets when widget is active on the page
- Saving of widgets so that it completes the process and changes JSON-LD on first load save, thanks to Mathew and Craig for the report [107120,105176]
- Ensure that custom month recurrence rules (e.g. "every three months") are respected, and the events are generated on the correct dates (thanks to @applegateconnect and others for reporting this!)
Tweaks
- Combine widget css into a single css file, still using widget-calendar-pro-style has the handle
- Move Google Maps API loading to tribe_assets and only load once on single views and Map View when PRO is active, thanks to info2grow first reporting
- Added localization variables to scripts over the mini calendar widget, in order to avoid warnings when used on non events pages
Deprecateds
tribe_events_pro_google_maps_apiin favor of usingtribe_events_google_maps_api- Removed empty function
tribe_ecp_uninstall
Fixes
- When using "Once" recurring rule, events were not being updated correctly. Thanks to @lasandia, Cynthia Giles and others for flagging this!
- Fixed duplicate parameters in week view when using the shortcode
- Modify resource url function to work in mu-plugin directory, thanks to Doug for reporting it
- Correct behavior when using "day-of-month" recurrence rules, thanks to SiteCrafting for reporting this!
Tweaks
- Improve the translatability of recurrence description text by making generic words like "day", "weeks", "year", etc. translatable in more contexts
- Update the warning message for users who are breaking an event from the series, adding a note about possible 404s. Thanks Robert for reporting
- Move the WordPress Custom Fields Metabox show|hide settings to The Events Calendar
Fixes
- Enable recurrence rules to work on the initial date of recurrence, thanks to Matt for bringing this up.
- Fix month view shortcode to url when changing between months, thanks to ltcalendar for reporting
- Fix the view shortcodes to display the view titles, thanks to templodoser for the first report
- Modified the REST API root url for
/allto query for all events belonging to a series - Fix the Mini Calendar and Events Lists widgets styles in the customizer when previewed for the first time
- Not being able to disable Generate JSON-LD data for the Advanced Event List Widget, thanks Craig for the report of this
- Yearly exclusions description along with the different date option, thanks for the report Thomas
Tweaks
- Utilize future event display on the Countdown Widget to go to the next event once the current event starts
- Namespace javascript debug function to prevent conflicts causing a function found, thanks to Tom-Mulvey for the fix
- Updated the "Additional fields" settings page, improving the UX
Features
- New action after saving venue geodata to the database
Fixes
- Add back 3rd parameter to existing filter to prevent fatal errors with Yoast SEO and other 3rd party coding, thanks Laura