Changelogs

Avoid duplicate events when importing from some iCal, Google Calendar and Facebook feeds in Event Aggregator (our thanks to Jason Sears, controlyours and many other users for highlighting these issues) [67038]
Fixed bug that caused scheduled imports to get stuck in a perpetual state of failure when receiving error messages from the Event Aggregator service (our thanks to Antonio Jose and others for flagging this problem) [83767]
Resolved issue where errors from the Event Aggregator service were not properly logging/visible on the History tab [83767]

Made linked post fields’ auto-save features more stringently check for empty values to prevent the plugin from trying to “save” empty values (our thanks to Jean-Marie for highlighting this problem) [80282]
Moved the organizer e-mail address field label a bit to better accommodate Community Events [80426]
Added filter to tribe_get_display_end_date()’s return value [77730]
Avoid notice-level errors while processing queues within Event Aggregator (our thanks to David Sharpe and others for reporting this) [84020]
Improve compatibility and avoid Javascript errors when running alongside Twenty Seventeen [70853]

Multisite Support for Settings Exports
Added warnings to the Version Management settings page if the system or site configuration could prevent automatic updates from working as expected.
Added support for validating the Recaptcha hostname by using the ‘itsec_recaptcha_validate_host’ filter.
Refresh module settings after an import has been completed.
Notify the user of invalid file paths for Log Files, Backups and NGINX Conf file during an import.
Replaced file locking with database locking. This method of locking is compatible with all systems as it does not require the ability to write files. It also allows for locking to work on sites that have multiple front-end servers with a shared database. Since file locking is no longer used, the Global Settings > Disable File Locking setting was removed.
Add “Copy to Clipboard” functionality for server and wp-config rules.

Prevent 404s when following links in email notifications on a site with Hide Backend enabled.
Ensure uninstall process is not run when another version of iThemes Security is still active.
Fixed method of working around Hide Backend.
Warnings are no longer generated when saving a user profile with a role of “No role for this site” selected.