Implement double opt-in

Not so far. Mark this as Feature Request.

I would really appreciate this feature, too.

Ok, Work is in progress,

By the end of the week a new version should be available.

Hi, any news for double opt-in?

I second this feature request.
It has been quite a long week by now ;-)

Available in the new dev version.

As we had to revert the changes for the other tickets, this is still not implemented. I have a look on the solution discussed in IRC.

The attached patch implements a Double-Opt-In Feature by using the formsSendActivationMail from the CleverReach API. This means for the moment you have to select a preconfigured form from the CleverReach API (See screenshot).

This way you have a unique appearance of your confirmation mail when you use the embedded form anywhere else.

Reapplied patch after adding #2458481: Undefined index 'active' to dev.

Updated patch to fix form field description.

Patch applies cleanly against the latest dev-release. I added another line in cleverreach_subscribe_form() so the cleverreach.subscribe.inc is loaded when the form is rebuilt from cache (this is for example needed when the form should be submitted via Ajax). Attached you can find the extended patch and an interdiff.

Any news about this issue? Unfortunately in Germany it's prohibited (data privacy laws) using a newsletter service without a double-opt-in procedure :(

@dercheffe, did you test the patch?

I've started working on a 2.x branch (https://github.com/CandoImage/drupal_cleverreach/tree/7.x-2.x) which comes with a code skeleton for the API (Makes developing using the SOAP Service easier).
I just added this patch :) Thanks!

Patch #12 (or #11) does not apply cleanly against latest .dev release for me. That's curious because the patch is newer than the latest 7.x-1.x-dev release... I'll keep you updated.

Ok I finally found out that this line leads to the problem:

; Information added by Drupal.org packaging script on 2015-03-24
version = "7.x-1.0+6-dev"
core = "7.x"
project = "cleverreach"
datestamp = "1427217788"

The patch doesn't know that line... and I think that's OK in general.

Patch #12 works great against latest .dev and I'll set it RTBC hereby. Is there an active maintainer who could create a new release containing this very important patch for German customers?

Yea, i will update the stable release soon to 7-1.1

Thanks for the patch, added.

D8 Port here: https://www.drupal.org/node/2856329