Google Analytics for WordPress by MonsterInsights was updated to version 6.0.14, from version 6.0.4. Changelogs:
6.0.14
- Tweak: Allow for invalid license to be removed if debug turned on.
- Fixed: Issues with internal links being tracked as internal-as-outbound
- Fixed: Issues with tracking of downloads
- Fixed: Issue where optin tracking would opt-out on settings panel save
6.0.13
- Tweak: Better detection of issues with authentication due to an outdate WP version.
- Fixed: Issue where JS tracking inadvertantly turned on debug mode due to a bad string to boolean conversion.
6.0.12
- New: The JS events tracking has been moved to a new JS file instead of inline. This will offer the same performance as inlining under HTTP/2, but with the benefit of better cache bursting.
- New: Expanded admin adblock detection.
- Tweak: Select2 is now bundled as Select300 in MonsterInsights. We’re pulling down the latest copy of Selct2 and then on-the-fly renaming it. This should end any conflicts between our select2 boxes and other plugins/themes.
- Tweak: We’ve implemented better error detection on the authentication flow. Some users may have previously seen “No profile errors”, due to issues with their server setup will now see more accurate errors.
- Tweak: For servers that use PHP Object caching, the cache will now be flushed during the uninstall routines. This should solve a very rare uninstall error.
- Fixed: A “Invalid UA code” error was displayed whenever someone used oAuth2 and then saved the settings panel, despite having a valid UA code.
- Fixed: An issue with the lazyloading of the Google Client for frontend use has been fixed.
6.0.11
- Notice: Version numbers 6.0.5 – 6.0.10 were not used, as we’re synching the version numbers of the Lite and Pro versions of our plugin. You didn’t miss any updates.
- Notice: As of this release, we no longer backport changes to the old yst_ga option. If you need to access MonsterInsights’s settings programically, please use our helper functions. Do not directly access a option.
- New: Redesigned authentication dropdown that shows the site urls to make it easier to find a profile when the users have many accounts.
- New: Tracking is now enabled for the WordPress admin login page (wp-login.php).
- Tweak: The Google class in the admin now only checks for blocking when the reauth is attempted. Expect to save a ton of external calls in the admin, and maybe a performance boost.
- Tweak: The GA client object is now lazyloaded on the frontend, so it’s loaded only when something (like another plugin) attempts to use it. In plain English, this will make a alot of sites load times significantly improve.
- Tweak: The analytics.js output has been tweaked to be slightly more asthetically pleasing (its aligned correctly). We realize no one probably cares but we look at this code for every user we support, so it help us.
- Tweak: The config expired notice has been updated to reflect that it can also be shown if the server is blocking MonsterInsights’s ability to connect to Google Analytics.
- Tweak: The cron jobs for opt-in tracking and statistics have been combined into a single cron.
- Tweak: Various performance improvements in the frontend output class.
- Tweak: A notice is now shown when MonsterInsights rejects a manual UA code from being saved for being an invalid format.
- Fixed: Issue where the plugin TweetShare would prevent users from being able to see their properties in the authentication dropdown.
- Fixed: Issue where the manual UA code might not be ported as we were backporting changes to the monsterinsights_settings option to the yst_ga option for backwards compatibility. This lead to a situation where the new settings would override the old ones before the routine to fix the manual UA code issue had run.
- Fixed: Issue where a fatal error from a reference to a class called “Yoast_Frontend_GA” which our plugin doesn’t have or use, would be shown caused by the previous Yoast usage of object caching via an autoloader. This is solved by doing a 1 time object cache flush on upgrade.
- Fixed: Issue where if you had more than 1000 profiles on your Google account, not all would be shown.
- Fixed: App analytics properties are now excluded from the dropdown of properties you can authenticate to.
- Fixed: The readme suggested a filter to use for filtering the UA to use, but the filter name was typo’d. This has been fixed.
- Fixed: Issue where the tracking cron would add a new unique cron each day.
- Fixed: We implemented a routine to cleanup those extra crons as well as the old yoast one we no longer use.
- Fixed: Issue where the .org theme Schema would prevent users from being able to see their properties in the authentication dropdown.
- Fixed: Issue where JS based events tracking might not correctly track a mailto: link.