Recent comments

๐Ÿ‡บ๐Ÿ‡ธUnited States adanbouzoua

I am testing trying to run vartheme_bs5 and storybook.
If you have components files inside vartheme_bs5 if not copy them from modules/contrib/varbase_components/components. I found my setup with empty folders.

I am also having an issue with the components and the storybook.
I am getting

Error: Failed to fetch
  at StoryRender.renderToCanvas [as renderToScreen] (/vendors-node_modules_lullabot_storybook-drupal-addon_dist_preview_mjs-node_modules_storybook_-27753f.iframe.bundle.js:888:1045))
  at /sb-preview/runtime.js:81:10850
  at StoryRender.runPhase (/sb-preview/runtime.js:81:8772))
  at StoryRender.render (/sb-preview/runtime.js:81:10783))

And
Access to fetch at 'http://varbase.ddev.site/_cl_server?_storyFileName=.%2Fdocroot%2Fthemes%2Fcontrib%2Fvartheme_bs5%2Fcomponents%2Fatoms%2Fheading%2Fheading.stories.json&_drupalTheme=undefined' from origin 'http://varbase.ddev.site:6006' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

I did all the CORS configs as recommended, but the problem still needs to be solved. I am using DDev and follow the steps in the tutorial. Storybook 7.6.20 for server-webpack5

๐Ÿ‡บ๐Ÿ‡ธUnited States adanbouzoua

adanbouzoua โ†’ made their first commit to this issueโ€™s fork.

๐Ÿ‡บ๐Ÿ‡ธUnited States adanbouzoua

A related issue in Google Tag
Script placement differences between 1.x and 2.x
https://www.drupal.org/project/google_tag/issues/3451427 ๐Ÿ’ฌ Script placement differences between 1.x and 2.x Active

๐Ÿ‡บ๐Ÿ‡ธUnited States adanbouzoua

adanbouzoua โ†’ changed the visibility of the branch 3451427-script-placement-differences to hidden.

๐Ÿ‡บ๐Ÿ‡ธUnited States adanbouzoua

adanbouzoua โ†’ made their first commit to this issueโ€™s fork.

๐Ÿ‡บ๐Ÿ‡ธUnited States adanbouzoua

Update
The previous test was done with Google Tag Version: 8.x-1.6 and Datalayer 2.0.1
Changing Google Tag Version: 8.x-1.6. >> Version: 2.0.2 fix the issue

Conclusion: Datalayer 2.0.1 + Google Tag 2.0.2 has no issue. The module works with Google Tag version 2 but not with Google Tag version 8
---
dataLayer.push allows the snippet elsewhere than inside .
It seems that it has been implemented on Google Tag 2.0.2 but not 8.x-1.6

Data Layer declaration vs dataLayer.push
By adding a dataLayer snippet above the GTM container snippet. This step is called โ€œData Layer declarationโ€.
Or by pushing data with dataLayer.push method.
https://www.analyticsmania.com/post/what-is-data-layer-in-google-tag-man...

๐Ÿ‡บ๐Ÿ‡ธUnited States adanbouzoua

The version 2.0.0 has not bug related to snippet placement.
The bug was introduced with the version 2.0.1

Production build 0.71.5 2024