Weave Code
Php Sdk Laravel Package
commercetools/php-sdk
Deprecated PHP SDK for commercetools Composable Commerce. Provides native PHP models/helpers, IDE autocompletion, object mapping, i18n, and an OAuth2 client with caching and async/concurrent request support. Requires PHP 5.6+ (Guzzle).
The e-commerce SDK from commercetools for PHP.
Frequently asked questions about Php Sdk
- Why is this commercetools PHP SDK deprecated, and should I still use it in Laravel?
- This SDK was deprecated on September 1, 2022, and replaced by commercetools' PHP SDK V2. Using it introduces technical debt, security risks, and incompatibility with future API changes. Migrate immediately to avoid breaking changes or missing features like GraphQL support.
- How do I install this deprecated SDK in Laravel?
- Run `composer require commercetools/php-sdk`. However, note this requires PHP 5.6+ and lacks Laravel-specific optimizations. You’ll need to manually configure OAuth2, caching, and dependency injection (e.g., via Laravel’s service container).
- Does this SDK work with Laravel’s service container or dependency injection?
- No, it isn’t natively integrated with Laravel. You’ll need to manually bind the SDK’s `Client` or `OAuth2Client` in your `AppServiceProvider` or use a facade wrapper. Laravel’s container (PSR-11) can be leveraged, but no built-in support exists.
- Can I use this SDK with Laravel’s caching system (e.g., Redis, file cache)?
- The SDK supports PSR-6/PSR-16 caches but defaults to APCu. To integrate with Laravel’s `Cache` facade, wrap SDK calls with `Cache::remember()` or create a custom adapter layer. No native Laravel cache driver integration exists.
- What Laravel versions are officially supported by this SDK?
- The SDK itself supports PHP 5.6+, but Laravel compatibility is unofficial. It may work with Laravel 5.6+ (PHP 7.0+) but lacks optimizations for newer Laravel features like attributes, enums, or first-party HTTP clients. Test thoroughly.
- How do I handle OAuth2 authentication in Laravel with this SDK?
- The SDK includes an `OAuth2Client` for client credentials flow. For Laravel, manually configure token storage (e.g., in `config/services.php`) and rotation. Avoid Laravel Passport/Sanctum unless you abstract the SDK behind a service layer.
- Are there alternatives to this deprecated SDK for Laravel?
- Yes, migrate to **commercetools/php-sdk-v2**, which supports GraphQL, modern PHP features, and Laravel-friendly patterns. For legacy systems, consider wrapping the SDK in a service layer to isolate dependencies and ease future migration.
- Does this SDK support async/queue-based requests in Laravel?
- The SDK supports concurrent/async requests natively, but Laravel integration requires manual work. Wrap SDK calls in Laravel queues (e.g., `dispatch()`) or use a job class. No built-in queue worker or event listeners exist for commercetools.
- How do I map commercetools models (e.g., Product, Order) to Laravel Eloquent?
- The SDK uses active-record-like models. To sync with Eloquent, manually map SDK responses to Eloquent models (e.g., via `Accord` or custom repositories). Avoid direct SDK model usage in Laravel’s ORM layer to prevent tight coupling.
- What’s the risk of using this SDK in production for Laravel apps?
- High risk: No future updates mean security vulnerabilities (e.g., OAuth2 flaws) and API incompatibility. Missing features (GraphQL, WebSockets) limit scalability. Plan a migration to SDK V2 with a parallel integration strategy to minimize downtime.
Weaver
How can I help you explore Laravel packages today?