Contrib.social

Onboarding is BROKEN - workaround downgrade to 2.0.0 to set up GTM

Open on Drupal.org →
Created on 24 October 2024, 2 months ago

When attempting to install a GTM-xxxxx container id on a fresh 2.0.6 install, there is an error, the UI changes briefly to show the GTM id and some additional options, then it disappears.

This got me thinking that if I downgrade to the original 2.0.0 release it would accept the GTM container id and this worked. I was able to upgrade from here and everything seems to be working.

Apparently there should be a test for entering a new GTM id on a fresh install to prevent this from recurring in the future.

Also, I believe that the instructions

This ID is unique to each site you want to track separately, and is in the form of UA-xxxxx-yy, G-xxxxxxxx, AW-xxxxxxxxx, or DC-xxxxxxxx. To get a Web Property ID, register your site with Google Analytics, or if you already have registered your site, go to your Google Analytics Settings page to see the ID next to every site profile. Find more information in the documentation.

should be updated to reflect that the GTM id can be entered as well.

🐛 Bug report
Status

Active

Version

2.0

Component

Code

Created by

🇺🇸United States davemaxg

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @davemaxg
  • Comment about 2 months ago →
    🇺🇸United States emjayess

    Same experience. Except that I completely removed the 2.0.x version and deployed the 1.x version, in order to get GTM connected and functioning as expected.

    This project has one job, to integrate with GTM, and it fails out of the box. How does this get past even the most elementary of quality assurance steps?!

  • Comment about 1 month ago →
    🇬🇧United Kingdom Sophie.SK

    We've had a similar issue - upgrading from 1.7.0 to 2.0.6 caused our scripts to stop being added to the page. Removing all conditions resolved the issue.

    I've linked another issue, 🐛 script embed breaking Active , which has a patch attached and may resolve the problem?

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024