Recaptcha & Newsletter Block
How can we use the Captacha / Recaptcha modules with the Block Newsletter ?
it will help us to filter spam …
A Captcha would be super great! Hope to find a solution by the TB team
That would be terrible!
I know about these things… but can we have a real, functional double-opt-in solution then?
We have no plans for that. Use a service like Mailchimp if you need to keep you mailing lists clean. It constantly rates email addresses and allows you to filter the low quality ones.
OK thank you for response on this and your time!
with an eye on the coming GDPR, which is necessary for the whole EU on 25. May 2018, i will ask again if there is any possibility for an Double-Opt-In for the contact and also for the newsletter form ?
This is absolutely necessary to go on with these forms from 25. May on.
Please find also some informations here:
Adding a double opt-in to your contact form is both unnecessary and will put off your customers, unless you immediately want to use that email address for marketing purposes. You will have to add some additional code to the contact form in that case, but I recommend not to do that.
If you use the native
blocknewslettermodule for signups, enable the switch at the top of the module’s configuration page. If you are using external marketing tools like MailChimp, do not enable the option, but instead follow the instructions that are provided, i.e. https://kb.mailchimp.com/lists/signup-forms/about-double-opt-in for MailChimp.
Disable both the newsletter and opt-in checkboxes via the config page “Preferences > Customers”. EU businesses are no longer allowed to opt-in customers via the terms and conditions.
And, voila, you are GDPR compliant.
thank you for your helpful answer. With this, i could manage the DOI for newsletter (i use the native blocknewsletter module at the moment, now the DOI works fine).
But there is the need to inform the customer that his name and e-mail-address will be saved when he is sending some things via the contact form to us.
For logged in customers the data and inquiry also will be saved in the BO and/or can be answered by external e-mail-software.
There should be a checkbox, even when we “only” save his inquiry and give an answer, i think this is the intention of the GDPR. When we use his e-mail-add. for marketing, then the situation is clear.
I am correct with my idea about the checkbox at the contact form (honestly i have to say i thinks so) ?
Are people stupid enough to think that sending a contact form with their email address does not get their email address saved? Are their monkeys using computers in europe?
@drmasterchief for most companies in the UK it will be sufficient to have a dedicated GDPR page detailing exactly what is and isn’t saved. You don’t need to edit the code to comply with it, you just need to tell the customer what is being saved and how it is used.
Hi again, regarding this thing with contact_form and your work on 1.0.4. with GDPR-module… another question:
“Strongly recommended” means, that there is no actual judge from a court about this and to prevent from some bad guys it is much better to have such an text with checkbox on the contact form.
Will the tb GDPR module for 1.0.4 include such a solution?
I am not following, what do you mean?
will this include such a solution and/or do you think about it?
A solution for what, that is what I am not understanding.
This is to obviate against hasty bills from lawyers and protracted discussion with them regarding this.
Maybe it is not that much work to include such thing in the contact-form?