Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @oriver,

    Greetings from CookieYes!

    Our plugin relies on JavaScript for its functioning, and as a result, it is not feasible to include an HTTP header. This is due to the requirement of modifying the values of the cookies associated with the plugin from ‘No’ to ‘Yes’ when the user consents to the relevant categories. The problem mentioned is inherent to all plugins that utilize JavaScript for their operations.

    Let us know if there is anything else we can help you with.

    Here is a temporary solution:
    https://www.ads-software.com/support/topic/missing-the-possibility-to-set-secure-attribute-on-cookies/#post-13811035

    Webtoffee: Why don’t you fix the problem?
    If the temporary solution works, then you should be able to fix it as well.

    • This reply was modified 1 year, 6 months ago by hannio.
    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi@hannio,

    We have released a revamped version of our plugin that addresses the issue you mentioned. If you are interested in experiencing the enhanced features and improvements of the new version, we recommend migrating to it.

    Migrating to the revamped version does not require you to start from scratch or lose any of your existing settings. We have prepared a detailed article that provides step-by-step instructions on how to migrate your user interface (UI) seamlessly. You can follow the instructions in the article to ensure a smooth transition to the new version while retaining all your settings.

    Here is the link to the article: https://www.cookieyes.com/documentation/ui-migration/

    Thread Starter oriver

    (@oriver)

    @hannio @cookieyesteam

    Thank you both. Looking into this already.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Samesite Attribute – error warning on FireFox’ is closed to new replies.