indrek_k

This is now fixed in v1.0.3

Thanks for the feedback!

My apologies – the .pot file was left out of yesterday’s update. I’ve added it in v1.0.3, published just now.

Hi there!

The textdomain was originally intended to be ‘gdpr’ (when we started working on the plugin, there weren’t any others) and it was used along with ‘gdpr-admin’ to separate admin and front-end strings. However, it turns out that this was a bad idea so I removed the ‘gdpr-admin’ domain (using context instead to separate the strings). But since I didn’t notice the ‘gdpr’ slug is taken by Trew Knowledge’s plugin, it looks like I will have to change it again.

Thanks for the request! Will change it to ‘gdpr-framework’ in today’s or tomorrow’s release.

Okay, so apparently WP has a new set of online translation tools which I’m not familiar with. I need to look into this further.

Meanwhile, quick and dirty instructions for using poedit (which is just as simple): https://codelight.eu/wordpress-gdpr-framework/guide/translations-and-multilingual-support/

I will update this post and add it as a chapter in the guide.

Let me know if you have any additional questions!

Awesome. Which caching plugin are you using? I’ll see if we can add automatic compatibility and also a note to the readme that ‘this works’.

I’m going to mark this issue as resolved. If you have any other troubles at all, please let me know!

Also, if you’re happy with the plugin, we’d really appreciate a review!

Update: fixed the mixed up T&C and PP links with v1.0.2 – please update!
Also, please let me know if you’re still having issues with the Privacy Tools page.

> I also have a suggestion for the “identify yourself” version of the privacy tools page. It’d be great, if you could add a checkbox with the message along the lines of I accept the Terms and Conditions and the Privacy Policy there as well, since users will be providing us with their emails.
Technically, we’re currently not storing the emails anywhere, so I’m not sure if that is required. I will consult with our lawyer friends at Triniti, ask if this is necessary and get back to you.

Hi there!

Thanks for the request. I will look into this and get back to you within a couple of days.

Hi there!

Thanks for the bug report and sorry about this! The minimum PHP version that the plugin works with is 5.6.33. You are probably hosting your site on a server that is running an older version. Unfortunately, we cannot support outdated PHP versions.

If possible, I would recommend you contact your web host to upgrade. Even v5.6 is no longer officially supported and PHP7 is at least 2x faster anyway.

I’ve updated v1.0.2 to display a human-readable error message.

However, if you double-check and find that you have a newer PHP version, please reply to this post again and let’s sort the error out!

Hi there!

Thanks for the detailed bug report!

> I found that I have to wait about a minute(?) after receiving the email for the link to go to the version of the page with the options for requesting or deleting data.
Can you please test how long it takes to receive your forgot password email compared to this one? The plugin should be using the same mechanism for sending emails as the rest of your WP site. If you notice the forgot password email arriving significantly faster, let me know!

> at the top of the page there’s an error message saying that the link seems to have expired.
Are you using any cache plugins?

I will look into the rest of the issues you described today and get back to you.

Thanks!

Hi Mads!

I’ll publish a guide for translating the plugin properly tomorrow or Tuesday latest.

Thanks for the feedback! If you have any other issues or comments, please don’t hesitate to get in touch!

Got it – the email went to spam. I will review and get back to you asap.

Hi there!

Sorry for the troubles! Which email address did you use?

First of all, have you updated the plugin? We released an update today fixing a couple of minor issues.

> took me while to fix the plugin to allow translations but that’s working now.
What exactly do you mean – was there a problem with the translations? If so, where exactly? Which multilingual plugin are you using?

> my problem now is when user clicks button to delete data, he’s sent to a page to identify themselves by email. As soon user clicks “delete data” button the data gets deleted.
Can you please clarify this a little bit? Do you mean the “delete data” button in the WordPress Dashboard > Users > Privacy Tools or the one on the front-end Privacy Tools page? Is the user logged in or just authenticated via the Privacy Tools page?

I will double-check the deletion flow on Monday. There is currently no confirmation page after deleting, which is a bit confusing. This is scheduled in the next release within 1-2 days.

Thank you!

• This reply was modified 6 years, 10 months ago by indrek_k.

Hi there!

Thanks for the feedback!

Unfortunately, I don’t think we’ll be able to add support for Appointments+ in the near future. As it is not a very widely used plugin, it probably makes more sense to wait for WP’s official GDPR compliance update and then for WPMU’s own patch to make it compliant.

However, if WPMU doesn’t do this by themselves by the end of the summer, then we’ll definitely revisit this idea!

Hi there,

My optimistic release date was a bit pessimistic.
Would you like to take a look and test before we push the first version to the official WP plugin repository? You can find the plugin here: https://codelight.eu/formidable-gdpr.zip

What it does: it adds a new Settings tab to each Formidable Form called “Privacy”. From there, you’ll need to configure which field should be used as the primary email address for that form to identify data subjects. You can also exclude the form from being automatically included when downloading or deleting data.

We’ll add anonymization and consent tracking in a later release!

Any feedback is welcome. If something important feels missing, please definitely let me know!

• This reply was modified 6 years, 10 months ago by indrek_k.

Hi there!

Thanks for your request! This topic deserves a separate post, but to give you a brief overview, the upcoming ePrivacy Regulation sets new rules for cookies (again!) and pushes the responsibility of handling them properly more in the hands of the browser than the website. You can read more about this topic here: https://www.i-scoop.eu/gdpr/eu-eprivacy-regulation/#The_EU_ePrivacy_Regulation_and_cookies

So taking this into account, we’d prefer not to add any features that will have to be removed again in the near future. However, the last time I asked our lawyer friends at Triniti about this, there were multiple different opinions about what “near future” means. There’s a chance that the new ePrivacy Regulation won’t come into force for a while, which in turn means that we would be stuck with GDPR’s cookie handling rules.

We will postpone development on this at least until May and hope that by that time, we’ll have a better idea of what we actually need to do. But we are aware that this is an important requirement and it’s definitely in our todo list.

Let me know if you have any other questions!