• Resolved holafreak

    (@holafreak)


    Does anyone have an idea why my state doesn’t get updated once I accept all cookies? I’m using the Google Tag Manager (GTM) template.

    I did some research in the wiki and support threads but I can’t get my head around why it’s not working.

    Could this be related to this issue? https://github.com/pressidium/pressidium-cookie-consent/issues/126

    Once I accept all cookies the tag assistant registers it but it keeps saying “Declined”.

    The cookie consent tag looks as follows

    The Google Analytics tag seems to get fired but nothing seems to happen. Sometimes I can see a Google Analytics collect? request in my network tools in Chrome and sometimes not. Nothing appears in my Analytics ever though.

    Besides that, my setup includes an own trigger

    That then triggers GA4

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor overengineer

    (@overengineer)

    Hey, @holafreak!

    Quick question: Are you using the AI translations feature by any chance?

    Thread Starter holafreak

    (@holafreak)

    Hi @overengineer

    Thanks for the quick reply! Yep, I used Gemini to translate all the available text into German.

    • This reply was modified 5 months ago by holafreak.
    Plugin Contributor overengineer

    (@overengineer)

    Hey @holafreak,

    Thanks for following up!

    There’s a known bug when using the AI translation feature to translate all strings of a language at once. This can cause consent to be incorrectly reported as denied. We already have an open GitHub issue for this (#166) and a fix is ready (it just needs a bit more testing). It will be included in the next version, which should be released in the coming days.

    In the meantime, a temporary workaround is to delete the translated language and use the AI translate feature one text field at a time, instead of using the “AI Translation” button which translates the entire language. Though, I realize this is not ideal.

    Thank you so much for your patience and apologies for any inconvenience this may have caused! If you run into anything else, feel free to let me know.

    Thread Starter holafreak

    (@holafreak)

    Hi @overengineer

    Thanks for the tip, that actually solved it. Sorry that I didn’t see that bug report!

    With the full AI translation enabled it also seems to reset the state to always be “denied” for everything after a page reload/refresh. In case that’s somehow relevant to the bug report.

    Thanks for your great work and this plugin.

    Plugin Contributor overengineer

    (@overengineer)

    Hey @holafreak,

    Just wanted to let you know that version 1.9.0 is out and includes a fix for this. Updating to the latest release will resolve the issue with any existing AI-generated translations (no need to delete and re-create them) and the “AI Translation” button should now function properly, translating all strings of a language normally.

    I’ll go ahead and mark this as resolved. If you run into anything else, feel free to create a another topic 🙂

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.