aristotelisj

Coming to think of it better, an INPUT field of type TEXT (the email field), is VERY similar to an INPUT field of type CHECKBOX.
So if we warn the user below a checkbox or below a text field, before they click inside the field to change its value, it is virtually the same thing.

With GDPR we should inform the user:
1. if you fill in the email, you acknowledge that we will use it
2. how we will use it
3. how to find out more in the privacy policy
4. and provide an immediate opt-out with ‘NO THANKS’ (similar to unchecking a box)
5. and provide opt-out in the email (similar to unchecking a box)

Therefore I changed my GDPR text as follows:

<span class=”wcf_cf_gdpr_message”>Your email address and cart are saved so we can send email reminders about this order.<br>
By filling in your email address you certify that you accept our use of your data and that you have read and accept our privacy policy.</span>

Thank you very much for this plugin.
5 stars

Hi guys,

Change your message to this:
<span class=”wcf_cf_gdpr_message”>Your email & cart are saved so we can send email reminders about this order.</span>

And specify this in your child theme CSS:
.wcf_cf_gdpr_message {
font-size: 1.3em;
}
#wcf_ca_gdpr_no_thanks {
font-size: 1.3em !important;
}

OK got it
Thanks Keylor

Actually this is the problem.
According to the GDPR, the user has to CLICK TO ACCEPT receiving emails.
The way your plugin works is by CLICK TO REJECT receiving emails.
This is not GDPR compliant.
It is the same as receiving newsletters… we cannot add the customer to the newsletter unless they click a checkbox willingly ADDING themselves to the list.
Contrary to this notion, the way the plugin works now, it is already adding the customer to the abandoned cart email list and he has to click something to REMOVE himself.
Anyway just bringing it to your attention.
If you think I am mistaken about the GDPR policy in this regard, please say so.

Understand. It is only a matter of time to add the missing pieces.
Keep it up.
Thanks guys.

I meant if it was possible to ADD the woocommerce email into that list of fields, so it can be added to the emails. This email is the one specified in Woocommerce>Settings>Emails>From Address and is basically the eshop’s email.

Also I am trying to generate an abandoned cart and I cannot do it.
1. I clear the browser cookies.
2. I visit the store & accept all cookies
3. I add to cart
4. I go to checkout
5. I click paypal button and cancel&return to site.
6. I check my orders and I have none ‘Pending Payment’

Thank you

I have no idea why it happens. At least it is not anything critical and it only happens very rarely and only for a few seconds.
Anyway thanks for your input.

Keep in mind that I also physically have :
autoptimize_fd940218ee399629d5601010699a4755.css
autoptimize_fallback.css
autoptimize_snippet_eff184983dcabae2782a112fd2bdcb37.css
index.html
inside this folder …./public_html/wp-content/cache/autoptimize/css/
Similarly various js files inside
…./public_html/wp-content/cache/autoptimize/js/

This is to be expected though right?

Shall I tell them to stop caching something?
I am already speaking to their support.
What should I say?

Shall we dismiss this as a timing issue? It only occurs until the cache is rebuilt.
I am just letting you know to keep it in mind.

It actually exists on the file system as I exxplained. It is not a request.
M3TC caches it under …./public_html/wp-content/cache/page_enhanced/
As I said, when all is going well, the file is disabled:
/public_html/wp-content/cache/page_enhanced/mydomain.com/wp-content/cache/autoptimize/css/autoptimize_9e40abce223e270667c109cb356a76b4.css/_index_ssl.html_old
When not going well the file is changed to /public_html/wp-content/cache/page_enhanced/mydomain.com/wp-content/cache/autoptimize/css/autoptimize_9e40abce223e270667c109cb356a76b4.css/_index_ssl.html and this file is what is returned to the browser instead of what should be returned!
So when the browser requests autoptimize_9e40abce223e270667c109cb356a76b4.css it gets an html file containing the contents of _index_ssl.html.

Do you want to see it in action? Let me know.

I do not have another caching system – only w3tc & autoptimize.
This happens as mentioned above.
You may need to try a few times to catch it. As soon as you purge all W3TC caches (watch the circle going round the favicon of the tab-title), ALT-TAB quickly to another browser and CTRL-F5.
When this happens, /public_html/wp-content/cache/page_enhanced/mydomain.com/wp-content/cache/autoptimize/css/autoptimize_9e40abce223e270667c109cb356a76b4.css
will contain _index_ssl.html with the contents of a page on your site (mine is /journal).
Also /public_html/wp-content/cache/page_enhanced/mydomain.com/wp-content/cache/autoptimize/js/autoptimize_9e40abce223e270667c109cb356a76b4.js
will contain _index_ssl.html with the contents of a page on your site (mine is /journal).
Both 148KB.
Under normal circumstances these files are disabled (_index_ssl.html_old).
This is not a serious problem and only happens if you access the page too quickly after the cache is purged. A few seconds later it gets fixed when you CTRL-F5 a few times.
If you want I can give you access so you can see it yourself.
Let me know.

I do not have another caching system – only w3tc & autoptimize.
This happens as mentioned above.
You may need to try a few times to catch it. As soon as you purge all W3TC caches (watch the circle going round the favicon of the tab-title), ALT-TAB quickly to another browser and CTRL-F5.
When this happens, /public_html/wp-content/cache/page_enhanced/mydomain.com/wp-content/cache/autoptimize/css/autoptimize_9e40abce223e270667c109cb356a76b4.css
will contain _index_ssl.html with the contents of a page on your site (mine is /journal).
Also /public_html/wp-content/cache/page_enhanced/mydomain.com/wp-content/cache/autoptimize/js/autoptimize_9e40abce223e270667c109cb356a76b4.js
will contain _index_ssl.html with the contents of a page on your site (mine is /journal).
Both 148KB.
Under normal circumstances these files are disabled (_index_ssl.html_old).
This is not a serious problem and only happens if you access the page too quickly after the cache is purged. A few seconds later it gets fixed when you CTRL-F5 a few times.
If you want I can give you access so you can see it yourself.
Let me know.

Excellent thanks. That worked.