Andrew Welch

> Your solution in https://github.com/nystudio107/craft-seomatic/issues/1417 was to tweak the GA script in the tracking scripts area, but because we do not have access to the wrapping tag in that config...

Well, I see two choices, if I'm understanding the issue properly: 1) You can just manually put the GTM script in yourself, as you are the Consent Mode and CookieBot...

I'm going to re-open this to see if there's something more interesting I can do about it

Relevant here is also: https://developers.google.com/tag-platform/security/guides/consent?consentmode=advanced I think it's possible that if I bake this into the scripts in SEOmatic, this might get us most of the way there

@pixelmachine thanks I'll adjust the code to do that (but no, it's not related to this issue at all, because it's regarding gtag, not GTM, and it has nothing to...

@robzor So my idea on this would be that there's an additional script you can enable, but I don't _really_ want to get into adding every possible Cookie* implementation to...

> It actually seems that I overlooked quite a lot. The favicons package doesn't currently allow me to provide updated file paths, so most of the paths in the manifests...

> Notably, I just checked - it does modify the HTML file correctly, but the actual image files fail to be generated in dev mode - which is, I assume,...

PR made: https://github.com/josh-hemphill/vite-plugin-favicon/pull/4 * causes the plugin to only emit files if `command === 'build'` * Adjusts favicons.path to match `viteConfig.base + viteConfig.build.assetsDir` Also includes: https://github.com/josh-hemphill/vite-plugin-favicon/pull/2

Cool @josh-hemphill no worries, OSS shouldn't be a lodestone! Would you be okay with me publishing my fork on npm with the name `vite-plugin-favicon2` and crediting you? Reason is I'd...