Sign in below to join the discussion and then click Allow Access
-
1Kamil Grzegorczyk 6 years ago
That is great. I am looking forward to test it live ;)
-
Iain Poulson 6 years agoLet us know how you get on!
-
-
Indrek Kõnnussaar 6 years ago
-
1Yasir Jabari 6 years ago
that is great improvement, thanks
-
Iain Poulson 6 years ago
Thanks Yasir!
-
-
Craig 6 years ago
A good list of resources for this - https://twitter.com/smashingmag/status/999189181162250241
-
1Matt Ryan 6 years ago
Note to self... don't' install Anonymization Addon on local site and push to live ;-)
-
Iain Poulson 6 years ago
-
-
moxy 6 years ago
This is a great idea. How exactly does one set the constants WPMDB_ANONYMIZATION_USER_LOGIN_WHITELIST and WPMDB_ANONYMIZATION_DEFAULT_PASSWORD ?
-
Chris Howard 6 years ago
Great work, guys! Confused by one things still. Do we have to put GDPR compliance on our newsletter subscription links? I thought we did, but I don't see it here on yours. Or have you set it up to only show to those in the EU? Thanks
-
3Jong Castillo 6 years ago
Great tool! One question: is there a way to use regex for the constant "WPMDB_ANONYMIZATION_USER_LOGIN_WHITELIST"? Ideally, we would like to whitelist all logins for a group of people. This group tends to have similar domain emails. Also, is it possible to adjust the config file for the plugin to anonymize data in other non-WordPress tables in the same database?
-
Iain Poulson 6 years ago
Hi Jong, thanks! I've just released version 0.2 with a new filter for controlling how users are whitelisted - see https://github.com/deliciousbrains/wp-migrate-db-anonymization#configuration And checkout https://github.com/deliciousbrains/wp-migrate-db-anonymization#extending for extending the anonymization rules configuration for other tables / columns etc.
-
Jong Castillo 6 years ago
Thanks for the new feature for whitelisting users! I will definitely check it out. It looks like it does what I need. :) And thanks for pointing out the configurations! I should've elaborated a bit more on my question for it. This is my understanding of the configurations. function my_wpmdb_anonymization_rules( $config ) { $config['usermeta']['meta_value'][] = array( 'constraint' => array( 'meta_key' => 'dob' ), 'fake_data_type' => 'dateTimeThisCentury', ); return $config; } ... where
usermetais for the tablewp\_usermetaandmeta\_valueis for the columnmeta\_valueinwp\_usermeta. What if the table doesn't have a prefix likemy\_tableinstead ofwp\_my\_table? Would it take the following configuration regardless of the prefix? function my_wpmdb_anonymization_rules( $config ) { $config['my_table']['my_table_column'][] = array( 'constraint' => array( 'my_table_key' => 'dob' ), 'fake_data_type' => 'dateTimeThisCentury', ); return $config; }-
Jong Castillo 6 years ago
I'm going to move this to the Github repository: https://github.com/deliciousbrains/wp-migrate-db-anonymization/issues/16
-
-
-
-
Rafael Stone 4 years ago
The right of access for data subjects was one of the rights introduced under GDPR. In general terms, the General Data Protection Regulation (GDPR) provides individuals with the right to request information on how companies are handling their personal data. This is what the Data Subject Access Request (DSAR) entails. A data subject can make the request via an email, or a form (online), or in any other form of communication. Then, a company will verify the requestor’s identity and his data in its data ecosystem and lastly track the request to resolution. This process takes approximately 30-45 days.
-
shane watson 4 years ago
It is very interesting news. I was searching for this information and here i found similar to this. It's very helpful and informative.<a href="https://seersco.com/articles/data-subject-access-requests-dsar/">DSAR</a>