• Resolved biggreencoach

    (@biggreencoach)


    Hi,

    In Firefox, we get the error:

    Cookie “XXX” has been rejected for invalid domain.

    How can we fix this? I would rather not edit the plugin, since any update will overwrite it. Chrome warns that this is also an issue.

    Any advice?

    Thanks,

    BGC

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Adam Dunnage

    (@adamdunnage)

    Hello @biggreencoach and thanks for getting in touch. Could you please check this from a Chrome browser to see if you encounter the same or is this only happening in FireFox?

    Could I also check if this is having any impact on Site Kit on your site? If so, please could you explain the issue in more detail. Please also feel free to share your?Site Health information. You can?use this form?to share privately if preferred.

    Thread Starter biggreencoach

    (@biggreencoach)

    In Chrome, I get

    Third-party cookie will be blocked. Learn more in the Issues tab.

    Specifically:

    Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, reading third-party cookies will be blocked. This behavior protects user data from cross-site tracking

    So at the moment, it’s very much a FF issue but a quick Google search shows it’s affecting Google Analytics and FF a lot. I have also submitted the Site Info via the form.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @biggreencoach Thank you for sharing the added context to this. This warning is quite common and something you will see when opening many different pages using both Chrome or Firefox. You will likely see this also when opening a support topic in this forum for example.

    You can find some more information on this here. It’s related to third party cookies only and you should not see this as a direct result of the Site Kit plugin. As this isn’t a Site Kit specific issue I am limited in the support I can offer you for this.

    If you do notice an issue with Site Kit itself then please let us know and we will be happy to help you with that.

    Thread Starter biggreencoach

    (@biggreencoach)

    Thank you. How would I set the cookie to have these flags in them, within the plugin? Isn’t that where this is being set?

    SameSite=None; Secure
    Plugin Support Adam Dunnage

    (@adamdunnage)

    @biggreencoach This is not something that can be configured within Site Kit, but there are security or other plugins that could be used for WordPress to define a CSP with “SameSite” rules.

    Here are some plugins that may help you with this:

    I hope this helps with your question.

    Thread Starter biggreencoach

    (@biggreencoach)

    As the plugin is serving the Google Analytics code, it seems (to me at least) obvious that this should be configured within the plugin, and not have to rely on another plugin.

    Those plugins you mentioned have not been updated in a long time.

    It seems to make sense to have this on by default: https://developers.google.com/analytics/devguides/collection/ga4/reference/config#cookie_flags / https://developers.google.com/analytics/devguides/collection/ga4/reference/config#cookie_domain

    I guess I’m struggling to see why a plugin by Google is having issues with FF when the fix seems relatively easy, not to mention there will be an issue soon with Google Chrome.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @biggreencoach As mentioned above this isn’t something that can be configured in Site Kit. We are limited to support for the Site Kit plugin here. You may find some further help at the fixing WordPress forum with this so I’d suggest opening a topic there.

    I will also raise this with the internal team for discussion and if there are any updates from this conversation then I will add them here for you.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Firefox: Cookie XXX has been rejected for invalid domain.’ is closed to new replies.