- Can I install mlpz/mailchimp-bundle in a Laravel application?
- No. mlpz/mailchimp-bundle is a Symfony bundle, not a Laravel package; it has no ServiceProvider, facade, or publishable config/mailchimp.php. Composer may resolve only on legacy Symfony 2.x and PHP 5.x stacks, not on Laravel 10 or 11. For Laravel, use a maintained Mailchimp v3 SDK behind your own service provider and interface.
- Does mlpz/mailchimp-bundle support Laravel 10 or Laravel 11?
- No. The bundle was frozen at a 2014 release with Symfony 2.x components and PHP 5.3/5.4-era constraints, so dependency resolution against Laravel 10/11 and PHP 8.1+ will fail. There is no Laravel integration layer to adapt. Treat it as a reference implementation, not an installable dependency.
- Is mlpz/mailchimp-bundle still maintained?
- No. The repository is archived and the package is marked unmaintained, with a last release dated 2014-10-07. It has low ecosystem validation, around 54 stars and zero dependents, so there is no downstream bug discovery or security-fix path. Do not add it to a current production stack.
- Which Mailchimp API versions does mlpz/mailchimp-bundle use?
- It targets the retired Mailchimp v1.3 and v2.0 REST endpoints. Those APIs have been retired, so calls will fail regardless of code quality. This is an API-lifecycle failure, not something you can patch incrementally; modern integrations should use Mailchimp Marketing API v3.
- What is the difference between mlpz/mailchimp-bundle and a Laravel Mailchimp package?
- mlpz/mailchimp-bundle follows Symfony bundle conventions: an MZMailChimpBundle class, DependencyInjection extension, Configuration tree, and YAML service definitions. A Laravel package would expose a ServiceProvider, facade or injectable client, and config/services.php or publishable config. The bundle provides no Laravel HTTP abstraction, auto-wiring story, or test fakes for Laravel.
- Does mlpz/mailchimp-bundle work with PHP 8?
- No, not reliably. Its 2014-era constraints imply PHP 5.3/5.4 style and Symfony 2.x dependencies, so Composer resolution on PHP 8.1+ will normally fail on platform requirements. Even if forced, the pre-PSR-18 transport and untyped code are not suited to modern PHP. Forking would require rewriting the transport layer.
- Can I use mlpz/mailchimp-bundle with Symfony 6 or Symfony 7?
- No. It is built for Symfony 2.x conventions and components, so it is not compatible with Symfony 6/7 dependency constraints or modern container auto-wiring. There is no maintained upgrade path in the repository. For new Symfony work, use the official Mailchimp Marketing SDK instead.
- What should I use instead of mlpz/mailchimp-bundle for Mailchimp in Laravel?
- Use the official mailchimp/mailchimp-marketing-php SDK for API v3, wrapped in a thin internal adapter behind an interface such as MailchimpGateway. Register it in a Laravel ServiceProvider and configure it via config/services.php and .env. Consume only the interface so you can bind a fake in tests and swap ESPs later with a one-class change.
- How do I migrate from mlpz/mailchimp-bundle to Mailchimp API v3?
- Inventory behaviors rather than code: every member field, list ID, tag, and sync trigger currently used. Freeze new call sites, log real request and response shapes for one sync cycle, then define a domain interface such as subscribe, unsubscribe, updateMember, getMember, and batchUpsert that does not mirror the legacy wrapper. Implement it against v3, including status_if_new, status semantics, and PUT-based upserts.
- Does mlpz/mailchimp-bundle support testing, mocks, or Laravel fakes?
- No. It has no Laravel testing hooks, facades, or container bindings designed for fakes. Because it is a Symfony 2.x bundle with YAML service definitions, you cannot bind a fake through Laravel's container in the usual way. The testable pattern is to wrap the Mailchimp v3 SDK behind your own interface and bind a fake implementation in tests.