All the servers in my institute are sitting behind a web proxy, so modules can't access to the web without going through this proxy.
In this case, Mailchimp servers are not reachable because you can't configure the proxy address.
I wrote a patch to solve this problem: it allows you to define the parameters of the web proxy on the Mailchimp configuration page.
I'll post the patch in my next post in case someone else has the same problem.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | mailchimp_behind_proxy-1708226-2.patch | 5.09 KB | tlaurent |
| #1 | mailchimp_behind_proxy-1708226-1.patch | 4.43 KB | tlaurent |
Comments
Comment #1
tlaurent commentedHere's the patch I mentioned earlier, this is for 6.x-2.6.
Comment #2
tlaurent commentedOops, forgot something. This patch should work better.
Comment #3
psycle interactive commentedI needed the exact functionality that was described by this patch, my solutions runs behind a proxy and was previously unable to connect to the mailchimp api. Once i installed this patch the module was able to connect to the mailchimp api and worked perfectly.
I ran the module through coder and it did not reveal any code styling errors that do not already exist in the mailchimp module code base.
Comment #4
wiifmRelevant issue for Drupal 7 #1493900: Support HTTPS tunnels to Mailchimp through proxy servers
Comment #5
nrackleff commented“And now our watch [for support of the 6.x version of the MailChimp module] has ended…” With the end of Drupal 6 support, I’m sad to say we too must turn the page.
Fret not! The 7.x-4.x and 8.x versions come highly recommended. Both are using Mailchimp’s new API 3.0 and are being actively maintained. “What is dead may never die, but rises again, harder and stronger!”