Official APIv2 Wrappers are up

[jesse]

Full post and links over here:
https://groups.google.com/d/msg/mailchimp-api-announce/fwtz9Cer5i8/sqJb6eif0xoJ


jesse

[Stan Lemon]

The new api looks great!

Two things about the PHP api...

1. Supporting 5.2 seems silly, at this time it's reached EOL and even 5.3 is approaching EOL. My suggestion would be to drop it and similarly consider adopting namespaces instead of the PEAR underscoring policy.  I realize this is a big change, so it's most likely a "next" version sort of thing.

2. You have composer.phar committed into the repository and this is just silly.  I would strongly suggest removing it.

Thanks for your hard work!

Stan

[jesse]

1) Nope, totally necessary. Even only being 5.2+ worries me a tad - I still run into people with hosting providers on PHP4 - and we need to try to support the most possible folks. It is possible a totally separate wrapper that picks up newer PHP, non-backwards compatible stuff could see the light of day at some point.
2) gone.


jesse

[Sam Millman]

If those who are on PHP 4 have not been hacked yet then it is merely a matter of time.

It is the same as the IE6 movement, up until recently everyone supported IE6 because "people still used it" but the problem was that it caused numerous problems for web developers to support this (everything had to be backward compatible, unclean code, horrid code, coding nightmares) and those computers that did use IE6 were open to numerous day-to-day attacks from the internet that a newer browser would be able to protect them from easily.

And so the drive to stop IE6 (-8 for Facebook, Google, Amazon and many others) started.

It is the same case with API wrappers in PHP, AWS have discontinued their old namespaceless API, even removed it from their GitHub, and they are not the only one to take this move. It is sometimes the responsibility of the API creaters (think of Facebook and Googles  and even Amazons, since ecommerce sites are normally the last to enbrace none-backward compatible changes, motto here) to force individuals to not just be happy with an out of date, insecure version of PHP and to seek their lazy web host top actually take precautions to ensure the security and durability of ones own site and data. Through this method we are moving forward in browser technology instead of staying stagnent on IE6.

That is why it is sometimes good to push for a new version irrespective of what needs to be supported.

All PHP functionality is backward compatible as such there should never be problems upgrading PHP, hell I am admining sites written in PHP 4.0 running on PHP 5.5, using PHP 5.5 code where it is possible.

[Bruno França]

The python wrapper is failing to install (Ubuntu 13.04, Python 2.7.4):

$ sudo pip install mailchimp
[sudo] password for bruno:
Downloading/unpacking mailchimp
  Running setup.py egg_info for package mailchimp
   
Requirement already satisfied (use --upgrade to upgrade): requests>=0.13.2 in /usr/local/lib/python2.7/dist-packages (from mailchimp)
Downloading/unpacking docopt==0.4.0 (from mailchimp)
  Running setup.py egg_info for package docopt
   
Installing collected packages: mailchimp, docopt
  Running setup.py install for mailchimp
    error: file '/tmp/pip-build-root/mailchimp/scripts/mailchimp' does not exist
    Complete output from command /usr/bin/python -c "import setuptools;__file__='/tmp/pip-build-root/mailchimp/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-WDqXno-record/install-record.txt --single-version-externally-managed:
    running install

running build

running build_py

running build_scripts

error: file '/tmp/pip-build-root/mailchimp/scripts/mailchimp' does not exist

----------------------------------------
Command /usr/bin/python -c "import setuptools;__file__='/tmp/pip-build-root/mailchimp/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-WDqXno-record/install-record.txt --single-version-externally-managed failed with error code 1 in /tmp/pip-build-root/mailchimp
Storing complete log in /home/bruno/.pip/pip.log

[jesse]

python wrapper has been updated.


jesse

[Steven Cinquegrana]

The API throws error "The remote server returned an error: (500) Internal Server Error / Unable to load url tracking stats" with method "reports/clicks" if the campaign is sent and has no links. Surely it should just return zero rather than throw an error.

 

[Ahmed Samy]

For Symfony2 folks i have created this Wrapper

https://github.com/AhmedSamy/HypeMailchimpBundle

[jesse]

That's reasonable and has been updated - in the future, please start a new thread when you have things unrelated to the thread you may be considering posting in (like this, which has nothing to do with the v2 API wrappers).


jesse