igestalten

Oh, absolutely! Why would anyone expect companies to charge for their work and expertise? I mean, who needs to pay bills or run a business? I’m sure you provide your services completely for free too, right?

Same problem for me with version 3.2.4. “Deny all” Button is not working in IOS. Works fine in all desktop browsers.

This is exactly the task of the plugin!?

same…

same problem – fix works great! Thanks

1.2.3 fixed it for me!
Thanks a lot

Debug after Scan:

Debugging before uploads directory scan:
Peak memory usage: 18 MB / 18432 KB
Memory usage: 15 MB / 15498 KB (3% of the available memory: 512 MB / 524288 KB)
Time since start: 0.031409025192261 seconds

Debugging after uploads directory scan:
Peak memory usage: 18 MB / 18432 KB
Memory usage: 15 MB / 15499 KB (3% of the available memory: 512 MB / 524288 KB)
Time since start: 0.031425952911377 seconds

Debugging after table render:
Peak memory usage: 18 MB / 18432 KB
Memory usage: 15 MB / 15509 KB (3% of the available memory: 512 MB / 524288 KB)
Time since start: 1.0372700691223 seconds

Error es described appears after trying to import any folder (also on dry run).
Tested in different Browsers (FF,Chrome,Egde), WP 5.5.1, PHP 7.3

Error disappears when reverting to 1.2.0

@dekket

I think the discussion will go on for a while…

Therefore I′m interested how you will get consent before writing server-logs? or calling data from a CDN ( Webfonts, jQuery, Maps, …)? No-Plugin will do that reliable.

On the other hand you could argue with a legitimate interest (Art. 6 GDPR) to provide a working website.

Some of the requirements are absolutely weird – so there will be a lot of work for the lawyers and the webworkers…

That’s fine. But then it’s null and void because, well, GDPR removes the cookie law and replaces it with something even stricter.

I′ve read the GDPR several times in the last weeks – cannot find that part!?
“Cookies” are still handled in the E-Privacy Directive from 2002(!) and additional national laws. The E-Privacy update won′t be ready in May 2018.

– Allow the user to withdraw consent

Delete your cookies!

– Allow the user to not agree and thus not be served any cookies.

Leave the site!

So – according to a lot of lawyers – this is a good way to cope with the GDPR when you have updated your privacy policy.

updating to cf7 4.9 fixed the problem! thankyou