After few weeks of wandering in the legal limbo, it was time to translate this newly acquired knowledge into practical coding. After eight posts on the subject matter, it was also time to conclude this mini-series on the General Data Protection Regulation.
One of the idea circulating about the GDPR is that it requires consent for all types of data processing. Is this true or just a myth? Specifically, what should I do to make my WordPress comment form GDPR-compliant?
One of the main problem with modifying a theme directly is that any update will overwrite your changes. What if the solution to that problem becomes the source of another? There are two sides to the coin indeed.
The clock was ticking – few days left to become GDPR compliant. Fortunately, a WordPress GDPR-compliance team had worked diligently for months to help site owners to that purpose. On May 17, 2018, a privacy and maintenance release was ready – just in time!
The long-planned data protection reform was about to be enforced. Everybody was busy getting GDPR-compliant. Everybody but me! In the run-up to the date, I received an email about GDPR. GDP-what?
Unlike Twenty Twenty (the most recent default themes by WordPress), Twenty Seventeen does not come with a copyright notice by default. In fact, it displays a credit link that cannot be removed through the theme settings (i.e. Customizer). How to reclaim the footer area?