Releases: google/site-kit-wp
Releases · google/site-kit-wp
1.1.0
Enhanced
- Update usage of G icon in admin menu, dashboard widget and screen options to align better with WordPress admin UI. See #877.
- Add support for site verification via file as primary method while keeping site verification via meta tag as fallback, resolving potential site verification failures. See #836.
- Move checkbox above submit button in setup screen and banner for better accessibility. See #788.
- Use more secure nonce generation mechanism for the authentication service. See #756.
- Show PageSpeed Insights performance stats for every individual URL in its details view, accessible from Site Kit dashboard and admin bar. See #654.
- Display Tag Manager container names instead of IDs in dropdowns for more user-friendly selection. See #591.
- Remove redundant notification title for AdSense notifications. Props OisinOConnor. See #586.
- Always use root domain for AdSense site because subdomains are typically not supported. Props OisinOConnor. See #578.
- Add support for displaying the full Site Kit admin bar menu with stats also for AMP requests, by leveraging AMP's dev mode feature. See #438.
- Simplify AdSense account status detection as a base for easier future enhancements and fixes. See #427.
- Add a checkbox to allow disabling Analytics tracking for logged-in users, and introduce a filter to adjust the behavior programmatically. Props Paras16699. See #88.
Fixed
- Ensure that a newly created Tag Manager container is properly saved so that the module setup is completed. See #821.
- Improve detection of existing AdSense snippets to cover more variants of snippets. See #798.
- Only display the Reset button on the setup screen if there actually is something to reset, and provide a feedback notice. See #758.
- Update incorrect message in development setup flow referring to site verification instead of Search Console. Props AVGP. See #600.
- Only show Tag Manager containers that are relevant to the site's mode, and accordingly support AMP-first by only exposing AMP containers. See #470.
1.0.4
1.0.3
1.0.2
Enhanced
- Introduce Jest for JS unit tests, migrate existing tests, and improve various related infrastructure components. See #524.
Fixed
- Do not disconnect user when refreshing an access token randomly fails, and ensure the user sees an error message about any errors during the process. See #818.
- Fix error that could occur when setting up a new Analytics profile from the module setup. See #816.
- Fix bug where the site verification nonce was not sent to the authentication service. See #797.
- Fix false positive when detecting existing Analytics tags, which previously blocked users from completing the module setup. See #793.
- Ensure that
google-site-kit
translation strings in JavaScript files are maintained after minification so that they can be translated on wordpress.org. See #782. - Improve various translation strings by removing trailing spaces, adding a context, fixing capitalization, and more. Props pedro-mendonca. See #769.
- Remove irrelevant translation strings from codebase by eliminating
@wordpress/components
dependency. See #759. - Improve detection of existing Analytics snippet by covering a further variant that is used e.g. by the Analytify plugin. Props ernee. See #744.
- Improve UX and fix performance issues with excessive re-rendering in the module settings screen. See #742.
- Fix style issues in various data tables which previously would break out of their parent containers on certain device widths. See #480.
- Fix
Unknown error (code: checking requirements failed).
by resolving quota issues on the authentication service. - Improve stability of REST API request issued by the authentication service when setting up a new site.
- Fix
Method not allowed
error on the authentication service.
1.0.1
Fixed
- Ensure verification tokens and other plugin user data correctly get cleared when resetting the plugin before the user has authenticated. See #771.
- Fix bug where the verification tag sent from the service to the plugin would result in a 404 response, preventing the verification from being completed. Props theeducatedbarfly. See #765.
- Improve compatibility with sites that have a
http://
website address stored ashome_url
, but actually require HTTPS. Props drcrow. See #760.
1.0.0
1.0.0-rc.2
Enhanced
- Modify plugin activation banner for consistent UI with the plugin setup screen. See #673.
- Remove now unnecessary warning about the Google Cloud Platform app in use being unverified. See #641.
- Make full data request available to the respective
Module
class's response handler. See #558.
Fixed
- Show setup UI for authentication service also on consecutive requests to the screen. See #704.
- Fix bug where lookup for a matching existing Search Console property did not work for domain properties. See #702.
- Consistently capitalize acronyms in camel-case API parameters, variables, etc. See #668.
- Prefix all third-party PHP dependencies to resolve various potential incompatibilities with other plugins that bundle similar dependencies. Props archon810, ewanly. See #612.
- Fix semantic issue with button in plugin activation banner not properly linking to the setup screen. See #75.
1.0.0-rc.1
Added
- Add support for authentication proxy service, replacing the previous authentication mechanism using individual GCP projects. See #645.
Enhanced
- Add "Manage sites..." link in the user dropdown menu that allows them to revoke access on the authentication service. See #643.
- Implement splash screen content pointing the user to the authentication service. See #642.
- Remove now unused "API Credentials" box from the plugin settings and only keep the reset functionality. See #590.
- Remove first setup step for client credentials since those should only be provided via the authentication proxy or filter. See #560.
- Migrate PageSpeed Insights module to rely on OAuth with
openid
scope instead of an API key, and remove overall API key support. See #511.
Changed
- Remove old OAuth client credentials stored in the option in favor of using the authentication service, and inform the user about the change. See #646.
Fixed
- Fix incorrect PageSpeed Insights error message referring to a non-existing API key. See #687.
- Fix authentication service requesting partially incorrect scopes. See #677.
- Fix OAuth credentials not being handled correctly when not using the authentication proxy. See #676.
- Ensure that the site's reference URL (typically home URL) consistently is without a trailing slash. See #651.
- Fix invalid links for various Analytics top content widgets. See #598.
1.0.0-beta.1.0.8
Fixed
- Fix bug where the options to set up a new Analytics property or profile were shown multiple times. See #522.
- Fix bug where time-critical checks during setup flow, such as existing tag lookup, produced stale results due to over-aggressive caching. See #506.
- Ensure that post search links to the correct URL for development sites with a different reference URL. See #499.
- Fix infinite loading state when selecting an Analytics account without any existing properties. See #398.
- Ensure that a secondary administrator who does not have any Tag Manager accounts sees a warning that they don't have access to the currently selected account. See #346.
- Fix empty batch request being triggered after activating the PageSpeed Insights module. See #339.
1.0.0-beta.1.0.7
Enhanced
- Show admin bar stats also for home page and blog page, if available. See #312.
Fixed
- Fix insertion of AdSense snippet not being consistently enabled by default. See #556.
- Fix bug where it was unexpectedly possible to enable a module with unmet requirements. See #531.
- Ensure that available Analytics profiles are exposed in dropdown, correctly based on the property. Props martinkrcho. See #89.