dlx

Hi @fclaussen

although I set the cache expiry time to 12 hours I still have the same problem. When I delete the cache everything works fine.

Questions:
– what is the security token? (nonce?)
– for what reason is the security token needed to accept the terms?
– is there a way to stop this?

I set the cache expiry time to 6 hours now for testing.

Hi @fclaussen

I′ve verified this again to be sure a minute ago: All 4 options (delete, rectify, complaint & export-data) don′t work. The sender is fine (specified in function my_gdpr_do_not_reply_address()) but the content of the emails are blank.

If you don′t have Mailster – I′ll pay the bill for testing. Just let me know…

Hello!

I tried this solution but it did not help. The email send to the user still has no content. The template is applied – so the email has a design (header / footer), just the content section is blank.

Does the plugin send the text as plain text or html? I think the newsletter plugin will only use the plain text part – so if this is empty this might be the reason why (just an idea).

Hi @fclaussen

I′m having this issue using v2.0.6 now. Tested this on a private tab (not logged in). I′m having a caching of cause. Tried to solve this by setting the cache expiry time to 12 hours now – hope this helps…

Same problem here. E-Mail is being send to the user but content is blank.

I′m using Mailster to send emails: https://codecanyon.net/item/mailster-email-newsletter-plugin-for-wordpress/3078294
Mailster is set to use the template for all emails send by WordPress – works fine with all other plugins (e.x.: BuddyPress, Formidable).

Plugin version: 2.0.6

Hi @fclaussen

ok, I′ll try to clearyfy this. On a website there are usually two menus: On on the top on the page and one in the footer. The footer menu has links to “terms of use”, “imprint” and “privacy protection”. This information are mandatory in some countries to be linked directly on every page.

So now the initial bar (or the new reconsent bar) are displayed in a layer on top of the footer which causes these links to become unaccessable.

To access the links the user has to accept the privacy settings first but this is not ok. If a user does not accept it′s not possible to click the links in the footer – that′s a problem. So we need an option to close the bar. Otherwise we ge a legal problem…

Hope you understand what I mean.

Here are two texts that can′t be translated:

– Type your complaint here
– Type your rectification request here

From the server log:

[Fri May 25 05:28:31 2018] [error] [client 84.46.57.0] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 8388616 bytes) in /home/www/doc/domain.com/wp-includes/wp-db.php on line 2516, referer: https://domain.com/wp-admin/post.php?post=22&action=edit
[Fri May 25 05:45:32 2018] [error] [client 84.46.57.0] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home/www/doc/domain.com/wp-includes/meta.php on line 840, referer: https://domain.com/wp-admin/post.php?post=22&action=edit
[Fri May 25 05:45:32 2018] [error] [client 84.46.57.0] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home/www/doc/domain.com/wp-includes/plugin.php on line 449, referer: https://domain.com/wp-admin/post.php?post=22&action=edit

Maybe it′s good to know I have more the 9.000 users in the database.

Think it′s this error (from debug.log):

[25-May-2018 03:48:12 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home/www/doc/domain.com/wp-includes/meta.php on line 840
[25-May-2018 03:48:12 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home/www/doc/domain.com/wp-includes/plugin.php on line 449

Updated my privacy page and wanted to ask users for explicit consent again but the loading (turning wheel on the right side) does not stop. Looked on the console anf found an error 500.

From the console:
load-scripts.php?c=1&load[]=jquery-core,jquery-migrate,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,utils,jquery-ui-position,jquery-ui&load[]=-menu,wp-a11y,jquery-ui-autocomplete,underscore,wp-util,moxiejs,plupload&ver=4.9.6:4 POST https://domain.com/wp-admin/admin-ajax.php 500 (Internal Server Error)

Best regards,
Jan

Hi @fclaussen

Okay, this calms me down a bit. Thank you!
But BuddyPress is already fully supported, right?

I have already written to the developers of Formidable (a very good form system) and they will support the WP-GDPR tools directly in the next release.

When will version 2.0 be released? Hope that there are not too many adjustments, because we all have a lot to do with all sorts of changes at the moment…

Hi @artifex404,

thanks for your Feedback!

Yes, you are right, IP address anonymization would be great and a solution without cookies would be perfectly. The GDPR says the users have to opt in before any cookie tracking may happen. I think no user will opt in then, so an other way has to be found.

Keep up the great work!
Jan

Hello @fclaussen

Finally found a solution:

.registration #basic-details-section p:last-of-type label {
display: contents;
}

But using <div class=”privacy-policy”> instead of the <p> would be a better solution.

Best regards!

Hi @fclaussen,

I see there is a cookie set when the user clicks on the accept button:
gdpr%5Bprivacy_bar%5D = 1

So this solution should work (if the name ‘gdpr%5Bprivacy_bar%5D’ is always the same) with Comet Cache Pro depending on a cookie value:
https://cometcache.com/kb-article/introduction-to-dynamic-version-salts/

I′ll try Swift Performance next…

Hi @fclaussen!

I tried to change this, but then the other form elements look wrong.
Can′t you replace the <p> with a <div> that has a class?

<div class="privacy-policy"><input name="user_consents[privacy-policy]" id="privacy-policy-consent" value="1" required="" aria-required="true" type="checkbox"><label for="privacy-policy-consent">Du hast unsere <a href="/privacy-policy/" target="_blank">Datenschutzerkl?rung</a> gelesen und akzeptiert.</label></div>

instead of:

<p><input name="user_consents[privacy-policy]" id="privacy-policy-consent" value="1" required="" aria-required="true" type="checkbox"><label for="privacy-policy-consent">Du hast unsere <a href="/privacy-policy/" target="_blank">Datenschutzerkl?rung</a> gelesen und akzeptiert.</label></p>

This would help to edit the look only for this checkbox.