Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Great module and is working fine except I see that in MailChimp the IP addresses associated with subscriptions made via this module are all of my web server.
Is it possible for the module to instead pass on to MailChimp the IP address of the subscribing user?
This is important for providing proof of opt-in subscription. Otherwise, we will need to keep the webform submission log to retain the IP address with seems to me to be an unnecessary duplication of data.
Thanks.
Comment | File | Size | Author |
---|---|---|---|
#5 | send-client-IP-to-mailchimp-1978650-5.patch | 1.74 KB | mdixoncm |
#4 | send-client-IP-to-mailchimp-1978650-4.patch | 3.53 KB | mdixoncm |
Comments
Comment #1
mdixoncm CreditAttribution: mdixoncm at ComputerMinds commentedSo - some digging around in the mailchimp API docs - it looks like the value optin_ip needs to be set in the merge_vars that are sent to the subscribe call.
There is a rather cryptic looking line in the Mailchimp docs saying "Abusing this may cause your account to be suspended. We do validate this and it must not be a private IP address." - but with no more information on what abusing the field looks like.
I suggest we add an option to the mailchimp module to send the client IP address, which we default to NO - and then folk can enable the functionality if they are feeling brave :)
Comment #2
mdixoncm CreditAttribution: mdixoncm at ComputerMinds commentedI think this is actually something that needs doing against the mailchimp module, rather than the mailchimp webform module - moving project - hope this is OK.
Comment #3
mdixoncm CreditAttribution: mdixoncm at ComputerMinds commentedComment #4
mdixoncm CreditAttribution: mdixoncm at ComputerMinds commentedFirst stab at a patch for this.
Comment #5
mdixoncm CreditAttribution: mdixoncm at ComputerMinds commentedFirst stab went a bit wonky - some whitespace issues in there - second stab looks a bit cleaner.
Comment #6
ruscoe CreditAttribution: ruscoe at ThinkShout for Mailchimp commentedWe're going to be ending support for the 7.x-3.x branch due to the upcoming deprecation of the v2.0 MailChimp API. If you're still interested in this feature, please could you recreate your patch for the 7.x-4.x branch?