- Issue created by @pookmish
- 🇺🇸United States pookmish
Looks like this starts at the container resolver and then issues propagate out to all the hooks. This likely will require some extensive refactoring.
- last update
over 1 year ago 48 pass, 2 fail - @pookmish opened merge request.
- 🇺🇸United States trackleft2 Tucson, AZ 🇺🇸
One use case for multiple containers:
We have a distribution that manages configuration for 1000's of sites, and do not want to override our core distro config just to add an additional container for our clients that have them, because that adds significant service, support and maintenance overhead.
- Status changed to Needs review
about 1 year ago 7:17pm 7 September 2023 - Status changed to Needs work
9 months ago 4:45pm 9 February 2024 - 🇺🇸United States japerry KVUO
Fair enough use case indeed -- however tests are failing so moving to needs work until that issue can be uncovered.
- 🇺🇸United States jeffreysmattson
This patch wont apply to current 2.0.x-dev version. When viewing the MR the page throws an error and comments and MR not viewable. How do we move forward with this?
- Status changed to Needs review
8 months ago 8:25am 5 March 2024 - last update
8 months ago 48 pass, 2 fail The last submitted patch, 9: 3376960-9.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- last update
8 months ago 48 pass, 2 fail - First commit to issue fork.
- 🇺🇸United States majorrobot
@chaitanyadessai's patch seems to be a reroll of !54, so I applied that locally.
I found that the code did not load multiple gtag script tags correctly. Multiple tags loaded, but each tag repeated the config of the first tag (except for that the tagId). This gave a 404 for those tags.
To resolve this, I took the pattern from google_tag_page_top() and refactored google_tag_page_attachments() accordingly.
gtm.js also needed to account for multiple tag configs, so I also refactored parts of that file.
Since MR !54 was out of date, I took the MR's branch and rebased on 2.0.x., then added my changes and pushed the new branch. I created MR !83. I'm not completely clear if this handles every case, but it should get us closer.
- Status changed to Needs review
5 months ago 1:57pm 4 June 2024 - 🇺🇸United States theMusician
Confirming this is still an issue in 2.0.5. Our use case is similar to trackleft2. We are able to work around this for now as we don't have many instances where we use multiple containers.