November 15, 2011 at 9:05 pm #4778BettorValueMember
I am posting this under general as I use the estore and affiliate platform and emember all of which integrate into several mailchimp lists in the same account. I got the following email today:
Your MailChimp account is using the login() API method which will be disabled in the near future.
This means code you are relying on will most likely stop working – in the mean time, your code will start running slower and slower.
If you are not a developer or programmer:
Are you using a plugin for your WordPress, Joomla!, Drupal, Magento, etc. site? If so, make sure you’ve upgraded to the most recent version, then ask the developers of it if they’ve fixed their code. If the code is publicly available, we can also take a look at it if you post the details of it in the API Google Group
For Joomla! in particular, we know that mod_mailchimp2 uses login() and has not released an update. Your options are:
if code doesn’t scare you too much, modify it like this
change to using the latest ChimpYourJoomla
check out the other Joomla! plugins available
Are you using one of our Mobile Apps? Make sure you are running the latest version of the iPhone and Android apps
Running Golden Monkeys or Chimpadeedoo? They are being fixed, so keep an eye out for updates.
If you are the administrative contact for this MailChimp account and are confused, please forward this on to your IT/technical folks, developer(s)
If none of that applies and you had a custom integration done, you may need to hire one of the experts listed here (or most any programmer familiar with your system – this is an easy fix)
If you are a developer or programmer, keep reading…
Your API implementation is using the login() method and should not be. You have used it 26 times in the past week, which is 26 times more than you should have
As previously announced here, delays are being added every time a call to login() is made.
This will cause your code to slow down.
As per the link above, the schedule for adding delays is:
2011-08-22 : 1 second delay will be introduced
2011-09-05 : 2 second delay will be introduced
2011-10-03 : 4 second delay will be introduced
2011-10-31 : 6 second delay will be introduced
2011-11-21 : 10 second delay will be introduced
< we’re not that mean, take your holidays >
2012-01-16 : bye, bye login() method
You can fix this by:
Hard coding an API Key into your code (that’s what login() returns anyway) and you are likely done – get an API Key here
Use the new OAuth2 support
Once your use of the login() method ceases, we will stop contacting you about this.
Need help or have questions?
Start a new thread in our Google Group – you can also review the thread started after the initial notification
Reply to this Email (this will like be slower)
I couldn’t find any info on whether this has been addressed or not.November 16, 2011 at 12:17 am #38518adminKeymaster
MailChimp just started this yesterday. They want you to use the API Key option rather than the normal “username” and “password” option.
eStore and affiliate had the “API Key” option already. We have updated the eMember plugin so that an API Key can be specified in the settings for this plugin too. Get a new build of the plugin(s) from here and you will see the API Key option in the settings:
Basically, specify an “API Key” in the autoresponder settings of the plugin and the plugin will use that (when you do that MailChimp won’t complain anymore).November 16, 2011 at 7:18 am #38519BettorValueMember
Cheers for that.
- You must be logged in to reply to this topic.