Weave Code
Adobe Campaign Client Bundle Laravel Package
lafourchette/adobe-campaign-client-bundle
Symfony bundle that integrates the Adobe Campaign client into your application, providing configuration and services for connecting to and interacting with Adobe Campaign APIs.
Provide access to adobe campaign API
Frequently asked questions about Adobe Campaign Client Bundle
- Is lafourchette/adobe-campaign-client-bundle a Laravel package?
- No. It is a Symfony bundle published by Lafourchette (Accor) that wires an Adobe Campaign API client through Symfony's DependencyInjection Extension and bundle registration. Laravel has no bundle concept, so composer require succeeds but nothing auto-registers, and there is no ServiceProvider, publishable config, or facade. Treat it as a source library, not an install-and-go Laravel dependency.
- Can I install this Adobe Campaign client in Laravel 10 or 11?
- You can run composer require, but the bundle will not bootstrap in Laravel. Laravel 10 and 11 ship some Symfony components such as console and http-foundation, but not the DI Extension and bundle machinery this package relies on. It will also pull symfony/dependency-injection and symfony/config into your dependency graph as dead weight unless you drive them manually. Plan to fork or extract the client instead.
- How do I integrate Adobe Campaign into Laravel with this bundle?
- Fork the repository, pin it to a specific commit SHA, and tag an internal release. Remove the DependencyInjection/ and Resources/config/ directories and any Symfony event subscriber wiring, then keep the client and transport classes. Add a thin Laravel ServiceProvider plus a config/adobe-campaign.php file, and bind the client as a singleton. That gives you a package you own and control.
- Does this package support PHP 8.2 and PHP 8.3?
- Compatibility is not guaranteed. The package has zero stars, no dependents, and no evidence of CI or test coverage, so PHP 8.2/8.3 support and PSR-18/PSR-7 modernization are not assured. After forking, add your own PHP constraint to composer.json and run PHPStan to surface PHP 8.x breakage immediately. Expect noisy deprecations from ext-soap on modern PHP.
- Which Adobe Campaign API does this client target?
- The underlying client targets Adobe Campaign's classic SOAP API with session-token authentication, using xtk:session logon and passing the token on subsequent calls. That API works but is legacy, and Adobe's roadmap steers toward Campaign v8 and ACC cloud with different surfaces. Before committing, confirm whether your deployment is v7 on-prem, v8 hybrid, or ACC, and whether your instance exposes the same endpoint and schema.
- Do I need ext-soap to use this Adobe Campaign client?
- Yes, ext-soap is a hard requirement because the client speaks SOAP to Adobe Campaign. That is a hosting constraint: verify the extension is installed and permitted in your containers, platform limits, and security policy. It also produces deprecation noise on modern PHP versions, so budget time for that.
- Is this package maintained and safe for production?
- Treat it with caution. It has zero stars and zero dependents, no community validation, no external bug reports, and no visible CI, test coverage, or security disclosure channel. It appears to be a byproduct of an internal Accor integration with a single-vendor, low bus factor. Assume you are the only consumer and that you will own the fork for the life of the integration.
- How do I test Adobe Campaign API calls in Laravel?
- The client is coupled to live SOAP endpoints, and mocking the xtk schema is painful. Confident integration tests usually require a non-production Campaign instance, which is often gated behind Adobe partner or support entitlement. Isolate the client behind an interface so you can swap the transport, and keep unit tests around your own adapter rather than the SOAP layer.
- What are the alternatives to this Symfony bundle for Laravel?
- The realistic alternative is to fork and extract the client, then wrap it in your own Laravel ServiceProvider; this is well understood and avoids framework bridging. Do not use a Symfony-bundle-to-Laravel bridge for a production marketing integration, as it adds an unmaintained shim between frameworks. If you are on Campaign v8 or ACC, evaluate Adobe's newer API surfaces and consider isolating transport behind an interface for an exit strategy.
- How do I configure Adobe Campaign credentials in Laravel?
- After forking, create config/adobe-campaign.php with your endpoint, login, password, and any API version settings, sourcing them from environment variables. Bind the client in a ServiceProvider and inject it where needed. Do not rely on the bundle's semantic configuration, because Laravel does not process Symfony Extension classes.
Weaver
How can I help you explore Laravel packages today?