Replies: 1 comment
-
Quick heads-up: you might want to redact the G-Tag in your shared config by editing your question and deleting the old revision afterwards. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Community, I wanted to ask for your advice before opening a bug, because I don't know if what I'm encountering is actually a bug.
We have enabled the Google Analytics integration and the cookie consent banner with GA + a custom cookie for YouTube in our documentation repository.
Additionally, I have configured the "Manage your cookie consent" link in the footer, and implemented an additional consent-link that is shown if the visitor did not consent to the YouTube cookies and lands on a page where we have embedded a YouTube video. The YouTube-iframe is only loaded if consent was given, otherwise there's a placeholder image and the consent-link.
The thing is, that this works perfectly on localhost (running in a docker-container), but on the Azure preview environment, it is not working properly.
On the Preview environment, the cookie consent banner opens correctly on first page load, but when clicking on the consent-link in either the Footer or the YouTube placeholder, the URL changes to "/#__consent" as needed, but the cookie banner stays hidden and is not shown.
I've tried troubleshooting this with an FE dev, but we got wildly inconsistent behavior, with the consent-banner sometimes showing for her, but not for me, sometimes only when clicking the YouTube-placeholder link, sometimes only when clicking the Footer link, then again when switching to another page or opening the Preview environment in another browser, it was not working again.
What could be causing this?
Here are my relevant code sections from our markdown project:
Mkdocs.yml:
Javascript for creating the YouTube-placeholder if consent is not given:
We also have some minor theme-overrides to enable Login into the documentation output via our own authentication service. This happens in custom.js, but I'm not sure if this has anything to do with the issue at hand.
Behavior on localhost:
Behavior on Preview environment:
If anybody has an idea of what is going on, please help. Any help would be much appreciated :)
Thanks, Birgit
Beta Was this translation helpful? Give feedback.
All reactions