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?!
Like the others, I attempted to deploy the 2.0.x version of this google tag manager module on a client site, and it's a non-starter; impossible to configure with a GTM-*** identifier.
* Attempting to enter and save a GTM-*** container identifier results in a flash of error and then simply resets the form with no useful error message whatsoever.
The project page indicates this project is sponsored/supported by both Acquia and Google, and it (a) does not work out of the box for GTM, and (b) is confusing as hell, with either missing or incongruent documentation across D.O. and GTM getting started or support docs. As this issue was reported all the way back in January, and remains unaddressed, it would seem to reveal that neither Acquia nor Google either cares or actually supports this module.
It was necessary to completely remove 2.0.x and roll with the 1.x version, to get tag manager connected and functioning. At this point, 2.0.x should just be flagged as unsupported.
Same problem, reported in issue #3418254 🐛 Upgrade to 2.0 failed, broke site: install hook(s) couldn't run; php 8 requirement not declared or evident Active .
And have encountered this painful upgrade blocker on a couple of projects now.
In issue #3421437 🐛 PluginNotFoundException: The "field_item:daterange_all_day" plugin does not exist. Active , I see there are others that encountered the same problem, and at around the same time.
This isn't just inconvenient, it blocks the upgrade path – seemingly because the entity or field update has never been correctly integrated or deployed in a compatible way for Drupal >8.7.
It *breaks* the site, *breaks* drush actions, and it is an utterly maddening thing to try and sort through. All just because some date fields need to change a little bit, but we're more or less left to guess and stab.
emjayess → created an issue.
emjayess → created an issue.