Skip to content

1.3.0

Choose a tag to compare

View all tags
@felixarntz felixarntz released this 13 Feb 23:41
1.3.0
3ec1129
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Added

  • Introduce googlesitekit.data registry for JS datastores. See #997.

Enhanced

  • No longer delete plugin data when uninstalling and instead rely on the more explicit reset functionality. See #1069.
  • Remove legacy migrations that were only relevant to pre-1.0.0 users. See #1062.
  • Migrate stray module settings into object-like option for consistency and future scalability. See #1030.
  • Introduce core/site/data/connection REST API route for retrieving site connection info. See #998.
  • Fully rely on Webpack for third-party dependencies and decouple from WordPress-shipped assets for more stability across all versions. See #993.
  • Inform the site owner about potential issues with their site that will likely cause problems when setting up the plugin. See #933.
  • Make opting in to tracking specific per user instead of per site. See #913.
  • Bump minimum required PHP version to 5.6, rely on up-to-date linting tools and fix various PHPCS issues. See #547.
  • Move REST route definitions into more applicable classes that handle the respective functionality. See #166.

Fixed

  • Allow users with existing Tag Manager accounts to create additional accounts during module setup. See #1080.
  • Fix partly outdated PHP files being served due to OpCache issues currently not addressed by WordPress core. See #1066.
  • Prevent unexpected PageSpeed Insights API responses from breaking the dashboard. See #1061.
  • Standardize GA tracking snippets and inconsistent data passed in events by introducing a proper tracking API in JavaScript. See #1055.
  • Fix several temporary blank screen errors by loading script dependencies more reliably via Webpack. See #1054.
  • Ensure that the Tag Manager snippet rendered is always compatible with the current context (AMP vs non-AMP). See #1036.
  • Do not render amp-auto-ads element in AMP stories because it is invalid in that context. See #979.
  • Ensure that Google Charts JS library is loaded as expected even when a window.google global already exists because of another library. See #939.
  • Do not refetch PageSpeed Insights data when the date range selector is changed, as its data its date-unaware. See #890.
  • Fix incorrect change arrow direction and color on "inverted" properties like bounce rate. Props WebFactoryLtd. See #481.
  • Add missing support for Search Console domain properties and rely on the correct property when requesting Search Console data. Props IgorCode. See #325.
Assets 2
Loading