GTM4WP 2.0.1 is out
GTM4WP 2.0.1 is a bugfix release: checkout step events no longer fire on the block-based Cart page, and a settings screen blocked by an ad or privacy blocker now explains what happened.
GTM4WP 2.0.1 is out on wordpress.org, so your site will receive it as a regular plugin update. It is a bugfix release for the 2.0 line with two fixes, both described below. The complete list of changes is in the GTM4WP 2.0.1 changelog.
Checkout step events no longer fire on the Cart page
On WooCommerce stores using the block-based Cart page, opening the Cart pushed the add_shipping_info and add_payment_info events into the data layer without any visitor interaction, and both events fired again on the Checkout page. The tracker recognized the Checkout page by the presence of a WooCommerce data store, and WooCommerce registers that store on the Cart page as well, so the Cart page looked like the Checkout page to it. The plugin now tells the tracker which of the two pages it is running on, and the checkout step events fire only on the Checkout page.
If your tags use these events, expect their counts to drop after the update: until now every visit to the block-based Cart page counted as both checkout steps, and the lower numbers are the correct ones. Stores using the classic Cart and Checkout shortcodes were not affected. Thank you to paulMolano for reporting the problem on GitHub.
A blank settings screen now explains itself
The GTM4WP settings screen is built in the browser by a JavaScript file that loads from the plugin folder. Some ad and privacy blocker filter lists, EasyPrivacy among them, block everything under that folder, so an administrator running a blocker with such a list opened the settings page and found it empty, with nothing anywhere saying why.
The plugin cannot override a browser extension, but it can say what happened. The settings page now shows a notice whenever the settings app could not start. It names the most likely cause and the way out: pause the blocker for the admin area of your site, or add an exception for it. The notice also appears when the settings script fails to load for any other reason, for example after an incomplete upload or with JavaScript disabled.
Please report problems in the support forum on wordpress.org or on GitHub.
