defining cookie purpose manually

  • Resolved k1024

    (@k1024)


    3 years, 11 months ago

    I’m running WP 5.6. I have installed the Complianz cookie consent plugin (v. 4.8.2) and configured it. The cookie scan completed and info on the detected cookies has been retrieved from cookiedatabase.org.

    I am trying to fine tune the cookie policy document (which will be in Polish) and in order to do this I have turned off the cookiedatabase.org connection. I can manually enter most of the info about each cookie but not the purpose (‘cel’ in Polish) – the dropdown shows no purposes (it only has a ‘choose purpose’ entry) and I cannot add any text to this field. The same happens when I add a new cookie and attempt to fill in the info manually.

    In the cookie policy document the description of the purpose under which all cookies are listed (also shown as ‘usage’ in the description of the service) shows up as ‘0’ (which I suspect may be related to them being functional/technical cookies).

    I don’t see any warnings or errors related to this in my admin panel or the DevTools console.

    So my question is – how can I specify the purpose for each cookie ?

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

    (@aahulsebos)

    Hi @k1024,

    You can turn on the cookiedatabase.org connection, and edit the cookies manually as well. The purposes are loaded from cookiedatabase.org, so the connection should be on for them to load correctly.

    You can disable “Sync cookie info with cookiedatabase.org” per cookie, and you will be able to use the dropdown and still edit manually.

    regards Aert

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    In addition to that: when you open the purposes drop down, you will see a search box. If you don’t have any purposes, you can type one here, then click ‘save’. The new, custom purpose will now get added.

    Thread Starter k1024

    (@k1024)

    Hi,

    That’s what I have been doing. It seems that I get all the info from the database except the purpose. For example, the scan has detected the cmplz_stats cookie and the synchronization with cookiedatabase.org resulted in information on the retention period (365 days) and the function (“store cookie consent preferences”) but the purpose field remains empty even though the database entry for this cookie lists the purpose as “Functional”. I’ve done the synchronization a number of times and observed no change.

    And when I turn off the per-cookie synchronization option and try to edit the purpose field manually I would expect to be able to choose a purpose (functional/statistics/marketing) or type in my own description of the purpose. But the dropdown list is empty and at the same time I cannot enter any text directly into the field – or rather I can enter text but I cannot save it.

    Best regards,
    Karol

    Plugin Contributor Leon Wimmenhoeve

    (@leonwimmenhoeve)

    Hi @k1024,

    Strange that this info is not synced from cookiedatabase.org. I just performed some tests with the same cookie and all seems to be working. We also did not receive any other reports about this cookie, which I would expect as nearly all Complianz users will use this cookie.

    The Cookiedatabase sync is limited to once per week, unless changes are detected in used cookies. This might be the reason that this correction isn’t synced right now. If you haven’t made a lot custom corrections under ‘used cookies’, you could try to clear all cookies via the scan and used cookies and issue a new scan + cookiedatabase.org sync.

    You can also manually add the purpose. Indeed we haven’t implemented the functionality to choose from used purposes. You can type this manually.

    Let me know if that solves the problem.

    Kind regards,
    Leon

    Plugin Contributor Aert Hulsebos

    (@aahulsebos)

    Hi @k1024,

    As for now, purposes are loaded from cookiedatabase.org (or should be loaded). If you deactivate the API, there’s not yet the option to manually add a purpose.

    Which purpose would you suggest, that is not available, or is covered by the current purposes?

    regards Aert

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘defining cookie purpose manually’ is closed to new replies.