Changelog

1.5.2

Release date: 21st May, 2019
* Tested with WordPress 5.2.
* Load accepted consents with JavaScript to improve performance.
* Use different text when all consent is required.
* When standard Consent bar/button colors are used, no empty attributes will be added to the elements.
* Bugfix: WP Registration integration now also works on Multisite, accepted consent on registration gets added to the ‘wpgdprc_log’ table.
* Bugfix: error shown in the WooCommerce order page is removed.

1.5.1

Release date: April 30th, 2019
* Bugfix: ‘token’ column not being added to access_request table for new users.

1.5.0

Release date: March 13th, 2019
* Bugfix: JavaScript error when no active consents are added.

1.4.9

Release date: March 12th, 2019
* Load accepted consents with AJAX so we can bypass any caching.
* Added consent placement ‘Body’. This will add code snippets directly AFTER the tag.
* Show a message for the administrators when using the [ wpgdprc_consents_settings_link ] and no active consents are added.
* Show the descriptions tab in the consents modal.
* Bugfix: Get correct charset collate when adding the ‘Log’ database table.
* Bugfix: Correctly handle cookies in multisite environments.

1.4.8

Release date: January 8th, 2019
* The consent description now allows HTML.
* Added ability to change the colors of the consent bar.
* Fixed bug where post ID was null.

1.4.7

Release date: December 17th, 2018
* Bugfix older PHP versions.

1.4.6

Release date: December 17th, 2018
* Added anonymised usernames.
* Added log table.
* Added integration for WordPress registration.
* Added warning in case the privacy policy page has not been selected yet.
* Fixed bug in the settings page.
* Fixed bug with session ID’s.

1.4.5

Release date: November 30th, 2018
* Hotfix: Fixed SQL syntax error.
* Added possibility to reset the consent bar.
* Consent bar will always be reset when consent is added/updated.

1.4.4

Release date: November 28th, 2018
* Anonymise requests after 30 days. This also removes the ability to process delete requests.
* Small bugfix to correctly strip slashes from ‘Consent’ titles.
* Added possibility to use external URL’s for the privacy policy.
* Added auto opt-in for admin’s when adding a comment.
* Fixed bug that added attachment to the consent bar when viewing an attachment.
* Fixed bug with token.

1.4.3

Release date: November 7th, 2018
* Security fix: Removed base64_decode() function.
* Security fix: Correctly escape input in $wpdb->prepare() function.
* Security fix: Only allow modifying WordPress options used by the plugin and by the user capabilities.

1.4.2

Release date: July 6th, 2018
* Added the ability to add required ‘Consents’. These Consents will always be triggered on page load.
* Added ‘Privacy’ column to the WooCommerce order overview.
* Added the ability to change the message of the required asterisk elements.
* Remove or re-add the GDPR fields from forms on plugin deactivation and activation.

1.4.1

Release date: June 12th, 2018
* Also show the WordPress Comments checkbox for administrators.
* Small bugfix in certain PHP versions.

1.4.0

Release date: June 8th, 2018
* Small front-end fixes.
* Added missing translatable strings.
* Fixed the text domain for some translatable strings.
* Show enabled consents of user.
* Small bugfix for admin redirects.
* Added the ability to remove ‘Consents’ via the admin panel.
* Added the option to wrap ‘Consents’ with tags.

1.3.9

Release date: June 3rd, 2018
* Small front-end fixes.
* Added translatable strings.
* Added shortcode ‘wpgdprc_consents_settings_link’. This will create a link to the consent settings.

1.3.8

Release date: June 1st, 2018
* Front-end bugfix.

1.3.7

Release date: June 1st, 2018
* Bugfix for admin columns at the comments panel.
* Fixed a bug when creating the database tables used by the consents functionality.

1.3.6

Release date: June 1st, 2018
* Added ‘Consents’ tab. Ask your visitors for permission to enable certain scripts for tracking or advertising purposes.
* Corrected the implementation of the multisite environment.
* Fixed an issue with the Gravity Forms integration and Pronamic.
* Larger input fields for checkbox texts.
* Hide WordPress Comments checkbox for administrators.
* Also anonymise WooCommerce data in user profiles.

1.3.5

Release date: May 24th, 2018
* Small bugfix for older WooCommerce versions.
* Small bugfix for some translatable strings.
* Bugfix to make sure the correct Gravity Forms field ID is determined.
* Added checkbox to the WooCommerce register forms.
* Hide WooCommerce orders section when plugin is inactive.

1.3.4

Release date: May 16th, 2018
* Fixed a bug when creating the database tables used by the request user data functionality.
* Fixed a bug when creating the request user data page.
* Expired access requests are shown more clearly.
* Improved error messages.
* Added a link to the support forum. We’re happy to help!

1.3.3

Release date: May 14th, 2018
* Fixed a bug that caused anonymise request mails to fail.
* Added missing translatable strings.

1.3.2

Release date: May 11th, 2018
* Added translatable ‘Yes’ and ‘No’ strings.
* Added confirmation mails sent after processing a anonymise request.
* Added mail sent to the admin when a new request is created.
* Added ‘noopener noreferrer’ to the Privacy Policy link.

1.3.1

Release date: May 8th, 2018
* Added a button to retry creating database tables required by the request user data functionality.

1.3

Release date: May 7th, 2018
* Added the request user data page. You can enable it in the Settings tab.
* The newly created page contains a shortcode which allows visitors to request their data. WordPress Users, WordPress Comments and WooCommerce orders linked to their email address are then send to that email address.
* The request user data page becomes the delete user page when visited through this email. The link in the email is available for 24 hours (cronjob) and linked to the visitors’ IP and current session.
* Delete requests end up in the new Requests tab. Click on ‘Manage’ to view a request and tick the checkbox to anonymise. Make sure to take care of these requests as quickly as possible!
* For WordPress Users ‘anonymise’ means first and last name, display name, nickname and email address are substituted by the corresponding field name in the database.
* For WordPress Comments ‘anonymise’ means author name, email address and IP address are substituted by the corresponding field name in the database.
* For WooCommerce orders ‘anonymise’ means billing and shipping details are substituted by the corresponding field name in the database.

1.2.4

Release date: April 3rd, 2018
* Show a notice when Jetpack is installed
* Fixed a bug with WordPress Comments

1.2.3

Release date: March 29th, 2018
* Storage of explicit consent timestamp
* Return of the settings tab
* Added ability to include your privacy policy page
* Added a couple of apply_filters()
* Small styling changes
* Added .POT file to translate this plugin (Thanks for translating!)

1.2.2

Release date: March 2nd, 2018
* Fixed a bug with WordPress Comments
* Added countdown to GDPR deadline (May 25, 2018)
* Added ability to add custom error messages to Contact Form 7 and Gravity Forms
* Added ability to add HTML tags to the texts and error messages

1.2.1

Release date: February 26th, 2018
* Fixed a bug with WordPress comments
* Fixed a bug with default checkbox texts

1.2

Release date: February 23rd, 2018
* Limit data shared with WordPress when updating the core.
* Added minimum supported version for Contact Form 7 (version 4.6)
* Added minimum supported version for Gravity Forms (version 1.9)
* Added minimum supported version for WooCommerce (version 2.5.0)
* Delete all data created by the plugin after deactivating integrations or uninstalling the plugin.
* Moved the position of the GDPR checkbox in the WordPress Comments form. (directly above the submit button)
* Moved the position of the GDPR checkbox in WooCommerce. (directly above the submit button)
* Removed the global “Error message” field.
* Fixed an issue with an older version of Contact Form 7.
* Small styling changes.

1.1.2

Release date: January 19th, 2018
* Added default error message.
* Small bugfixes.

1.1.1

Release date: January 16th, 2018
* Added screenshots.
* Added textual changes.

1.1

Release date: January 16th, 2018
* Added ‘Contact Form 7’ integration.
* Added ‘WooCommerce’ integration.
* Added ‘WordPress Comments’ integration.
* Small bugfixes.

1.0

Release date: November 4th, 2017
* Initial release.

54 Replies to “Changelog”

  3. Hi Balazs,

    Thank you!
    These are definitely features we want to include down the road. Will bump them up to the next sprint.

  8. Hi Guys this is really good so far as it goes. Great for comments too. But my understanding of the new law is that the check box in WooCommerce must be checked if customer agrees to, for example, receiving promotions by email/smailmail (I have to make explicit in the text box exactly what they are consenting to, and keep a detailed and dated record of this consent and how it was obtained). At present, the plugin does not allow them to leave the box blank, and thereby withhold this consent. As for granting permission to process their data to complete the order, that’s already in terms and conditions, for which WooCommerce has its own check box, so I don’t need this plug-in for that. So to cut a long story short, is there any way we can get an option on the plugin to allow the customer to leave the check box blank? THAT would be exactly what I need. Many thanks.

  12. Great work, guys!

    I second the requests for Formidable Forms and the Divi Contact Form, and would furthermore request Caldera and Elementor Forms as well.

    An important feature also seems to be the documentation of the user agreeing to having his data stored and handled. How is this handled in the plugin so far?

    Also, I second those requests by Balazs Revesz regarding exporting and deleting user data.

    Cheers!

    (I bet your active installations will explode leading up to May…)

    1. Hi Alex, thanks for your comment. In the next update we’ll focus on the user explicitly agreeing. Exporting and deleting user data is also set for the next sprint.

  14. Hi, add another request for Divi Contact Form module please & Caldera Forms, which I use extensively.

    Thanks!

  20. Hello,

    Nice plugin! I wish you add Divi Contact Form Module.
    I think it would be a good feature because … (i quote DIVI website below:)
    “437,821 Customers Are Already Building Amazing Websites With Divi.”

    Hats off for a job well done.
    Keep on going because it’s worth it!

    Dali

  25. 1) Formidable Forms [formidableforms.com]
    2) Thrive Leads [thrivethemes.com/leads/]
    3) Thrive Comments [thrivethemes.com/comments/]
    4) WP Ultimo [wpultimo.com]

  26. Beste,

    Bedankt voor de geweldige mooie plugin! Wij gebruiken ‘m op onze website.

    Ik wil graag nog een verzoek indienen omdat er een WordPress plugin staat nog niet in jullie rijtje staat bij de backlog.
    Wij gebruiken Tawk WordPress plugin voor live chat sessies op onze bedrijfswebsite.

    Willen jullie misschien ook Tawk plugin willen toevoegen aan de backlog van WP GDPR Compliance plugin?

    Voor meer informatie over de WordPress plugin:
    Tawk-website: https://www.tawk.to
    WordPress plugin van Tawk: https://wordpress.org/plugins/tawkto-live-chat/)

    Alvast bedankt!

    Met vriendelijke groet,
    Bas

  27. Hello, could you release any documentation as to how we could add our own stuff to it? I’m using a big sum of plugins each with their own capabilities that may or may not run depending on certain factors.

    1. Good one – we’ve added it to our backlog but will focus on expanding the plugin quickly at this time.

  30. This is great as far as it goes but the important other half of GDPR is that anyone who has submitted data to a site can download it or delete it – this would include visitors who have left comments. They have a right to remove any data held by anyone. Will you be addressing this in a future release?

    1. Hi John – Yes! This is our main focus when working on version 1.3 so stay tight. It’ll be here soon 🙂

  35. Hi,

    this is great work! I’d like to see you support “Easy Digital Downloads” since that’s probably an often used product.

  38. 1. Thrive Quiz Builder [thrivethemes.com/quizbuilder/]
    2. Thrive Leads [thrivethemes.com/leads/]
    3. Thrive Comments [thrivethemes.com/comments/]
    4. Ultimate Membership Pro [https://codecanyon.net/item/ultimate-membership-pro-wordpress-plugin/12159253]
    WP Social Login

  39. Will you be adding support for the WordPress WP-Ecommerce plugin, to comply with the GDPR?

    I think a simple checkbox on the checkout page would be great, if this is something that you would like to look at supporting in one of your updates?

    Kind Regards,

    Andrew

  41. Great plugin!

    Please add bbPress to your list.

    Next I think it is a good idea for you to participate in the discussion over at https://make.wordpress.org/core/tag/gdpr-compliance/
    A lot is going on over there to make WordPress GDPR compliant in its core. Although it is a great initiative to develop this plugin (and please continue) I personally think it is a better for everyone to have it in the core. Because I do understand that a lot of work has to be done before we reach that point I ask you to continue the great work.

  44. Thanks a lot for this plugin. Looking forward to use it on my client sites.

    I spent the last couple of days reading through DSGVO/GDPR stuff and took notes of all the things I have to do on all the sites I’ve built… these new legal requirements can really cause a headache.

    As quite some of my clients use Divi, I’d like to +1 for Divi Contact Forms.

    What do you think about adding these features?
    – Don’t store IPs of comments in DB.
    – Remove IPs of older comments from DB.
    – Remove/Disable Emoji code (as this adds a request to s.w.org).
    – Add an option to disable the “show avatars” option (already possible in Settings > Discussion, but very likely most of the the people are not aware that this request to Gravatar is also not really GDPR-proof).

    Is there any way to contribute to the plugin and e.g. create pull requests for new features? E.g. for numbers 1 and 3 above, there are already “copy-pasteable” solutions available, so they could be added quickly.

Comments are closed.