Ton of Cookies that shouldn’t be there

  • Resolved Nico

    (@gooloode)


    1 year, 6 months ago

    Hello,

    i just found 254 cookies on my website. First: They can’t be there, as i just now deleted all cookies & cache and reset the browser.

    Second: They shouldn’t appear anyway. All of these Cookies, from WP 301 Redirects Pro, as well as Elegant Theme’s Divi, are solely for Admin’s, are essential to the website and not visible to anyone on the Frontend, though they are shown. Most of them are one-time cookies set to save a post, which should be immediately deleted or ignored. Please fix that mass of non-existent cookies; i couldn’t even find them in the browser console.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @gooloode,

    These concern ‘administrator-only’ cookies used on the back-end, that Divi could set (to check which editors are available for the current post).

    Upon re-syncing with CookieDatabase (Complianz > Wizard > Consent > Cookie descriptions > Sync) they should be grouped together as one, and hidden from your Cookie List as it concerns admin-only cookies: https://cookiedatabase.org/cookie/divi-elegant-themes/et-editor-available-post/

    But I also see in your screenshot that they hadn’t been detected on your site in a few months. Perhaps you could start by deleting the current cookie list (Wizard > Consent > Cookie Scan) and performing a new scan entirely, and then “Sync” with CookieDatabase.

    Kind regards, Jarno

    Thread Starter Nico

    (@gooloode)

    Hi Jarno, thank you. I forgot to wipe the list before re-scanning. Upon scanning it kept the old ones and added the new, resulting in 250+ cookies. Though that begs the question, why Complianz hasn’t scanned and reset itself? I mean, 250 cookies is honestly record-worthy; i’m now at a whopping… 12. I have not deactivated the monthly search, nor have i manipulated Complianz in any way. Might there be a reason you could think of?

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @gooloode,

    I suspect that the Cookie List just had to be synchronized with CookieDatabase once more, in order for these et-available-post-* entries (which seems to have been the main culprit for such a lengthy list of cookies) to be correctly grouped, and flagged as being “admin only” cookies.

    Kind regards, Jarno

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Ton of Cookies that shouldn’t be there’ is closed to new replies.