Chapter in this post:
Due to a current ruling by the European Court of Justice (ECJ) on October 01.10.2019st, XNUMX, the cookie problem is boiled up again and, from the point of view of website operators, more topical than ever. Because currently, according to the judgment, only technically necessary cookies may be set when a page is viewed. The explicit consent of the user is required for the setting of further cookies - e.g. for advertising, social media content, comment functions, affiliates, etc. Here are a few hints and tips on the subject, but of course again with the note: I do not offer legal advice; If you have legal questions, it is best to contact a lawyer.
If a visitor's cookie is to be stored in the blog, on the news page, in your shop or elsewhere, which revolves around advertising, integrated social media content, affiliates or the like, you must first obtain consent; with the "I agree" button and so on. There is an extensive consideration of the case at the IT law firm. You will also find a look at the trade press at heise online.
If you have a website up and running yourself, then you probably know that the cookie problem is not that easy to understand. With WordPress websites you have the problem that WordPress sets cookies for both login and comments, which are saved directly when you visit the website. No cookie notice helps, because when it appears, the cookies have already been set.
In a future post I will introduce you to a solution (which I am currently still working on myself). Until then, you can determine which cookies are set by a - or specifically by your - website, both on the Apple Mac with macOS and on the Windows PC, for example with Google Chrome or Mozilla Firefox. Below are the instructions and a screenshot for each.
For this you need the add-on "Cookie Quick Manager", which you at this point can download. With the add-on you can see quite well which cookies are set on the respective website. It is also useful for developers that you can even use it to change, delete and reset cookies.
A note about Ghostery, which is recommended in some instructions as a tool to track down cookies: This only checks for cookies from known trackers and does not record any other cookies that are set by WordPress themes or plugins, for example. Because of this, it is not a good choice for the exam. Especially if you are working on a website yourself and want to adjust the information for users. Do you have a tip or a useful tool ready? Then please leave a comment on the topic! ;)
Jens has been running the blog since 2012. He appears as Sir Apfelot for his readers and helps them with problems of a technical nature. In his free time he drives electric unicycles, takes photos (preferably with his iPhone, of course), climbs around in the Hessian mountains or hikes with the family. His articles deal with Apple products, news from the world of drones or solutions for current bugs.