There's some functionality I'd like to have that isn't provided by the available Mailchimp modules: I have existing organizational content that I need to have automatically compiled and delivered weekly to team members.
What is the recommended approach for doing this? Should I write a module that depends on...
- Functions available in the Mailchimp and Campaign modules
- Only the Mailchimp PHP libraries
- Only the Mailchimp API
I have a working prototype script using functions like mailchimp_get_lists(), mailchimp_get_api_object(), and class methods like updateCampaign() and setCampaignContent() that I could simply place in a hook_cron. Are these expected to remain relatively stable enough for custom sub-module development, or should I work as directly with the Mailchimp API as possible?
Comments
Comment #2
samuel.mortenson@rblackmore I would say that relying on
mailchimp_get_api_object()
and the object methods returned by that is completely reasonable, the Drupal 7 APIs won't change and if you rely directly on https://github.com/thinkshout/mailchimp-api-php in any project you should expect the API to stay the same within a major version. Please re-open the issue if you have any other questions!