Closed (works as designed)
Project:
Google Tag
Version:
2.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Jan 2024 at 08:52 UTC
Updated:
11 Nov 2025 at 10:46 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
nortmas commentedI believe it's just a workaround.
Comment #3
eduardo morales albertiSame error here
Comment #4
summit commentedHi, will this patch be committed?
Comment #5
namisha jadhav commentedComment #6
anybodyPlease help fixing this issue as root cause: #3416508: Skip generating aggregates that won't be used for stale asset requests
Comment #8
anybodyI created a MR with the workaround from #5 until the core issue (#3416508: Skip generating aggregates that won't be used for stale asset requests) is resolved.
Basically, the core issue fix will have the same result as using the MR, at least as long as Drupal won't minify JS with
preprocess: false.Semantically the hotfix here is wrong, but technically it's fine.
Comment #9
sircosta commentedSame issue confirmed on a Drupal 10.5.4 production site.
The error occurs with JS aggregation enabled, and disabling it resolves the problem.
The workaround of setting { preprocess: true } on gtag.js and gtm.js fixes the issue permanently.
Comment #10
anybodyThis is NOT an issue in google_tag module! It's the linked core issue in combinatin with COOKiES / Klaro module!
See https://www.drupal.org/project/drupal/issues/3416508#comment-16340916 for details.
The attached patch does NOT fix it. So I'll close this one. Having
{ preprocess: false }WITHOUT, minified: trueis totally fine!