- Can this bundle work directly with Laravel, or is it strictly for Drupal Commerce?
- This bundle is Drupal-centric and not natively Laravel-compatible. It exports Akeneo PIM data to Drupal Commerce, requiring a custom Drupal module for integration. For Laravel, you’d need to either expose Drupal’s exports via an API (REST/GraphQL) or rewrite the logic for Laravel’s ecosystem (e.g., Eloquent, Spatie packages).
- What Laravel versions does this package support?
- This package doesn’t directly support Laravel—it’s designed for Drupal 7/8 and Akeneo PIM v1.x. If you’re using Laravel, you’ll need to abstract its functionality (e.g., via a microservice or API layer) or replace Drupal Commerce with a Laravel-native alternative like Sylius or Spatie Laravel Commerce.
- How do I install this bundle in a Laravel project?
- You can’t install this bundle directly in Laravel via Composer. It requires Drupal and Akeneo PIM. For Laravel integration, deploy the bundle in a separate Drupal environment (e.g., Docker), expose its exports via an API, and consume the data in Laravel using Guzzle or Laravel HTTP Client.
- Does this bundle support modern Akeneo PIM (v5.x+) or only legacy versions?
- The bundle is built for Akeneo PIM v1.x and may not work with modern versions (v5.x+). If using newer Akeneo, you’ll need to rewrite export profiles or use Akeneo’s REST API directly in Laravel (e.g., with webonyx/graphql-php or Guzzle) to bypass the bundle entirely.
- How do I handle product images/media in Laravel after exporting to Drupal?
- The bundle doesn’t natively handle media. For Laravel, you’d need to sync Drupal’s media (e.g., via Drupal’s media module) with Laravel’s storage (e.g., Spatie Media Library). Use Laravel Queues or chunked processing to manage large catalogs efficiently.
- What’s the difference between full and delta product exports?
- Full exports (`drupal_commerce_product_full_export`) re-export all products every time, while delta exports (`drupal_commerce_product_delta_export`) only sync new or updated products since the last run. Delta mode is more efficient for large catalogs but requires tracking export timestamps.
- Are there Laravel alternatives to avoid using this outdated bundle?
- Yes. For Akeneo PIM + Laravel, consider: 1) Using Akeneo’s REST API directly in Laravel (e.g., with Guzzle), 2) Migrating to Sylius or Spatie Laravel Commerce and building a custom Akeneo connector, or 3) Exposing Akeneo data via GraphQL (webonyx/graphql-php) for Laravel to consume.
- How do I authenticate Laravel with Akeneo or Drupal for data sync?
- For Akeneo, use OAuth2 (Laravel Passport) or API keys. For Drupal, if exposing via REST/GraphQL, use Drupal’s built-in authentication (e.g., Basic Auth) or Laravel Sanctum for token-based access. Ensure your Drupal module supports the chosen auth method.
- What are the risks of using this 2015 package in production?
- High risks include deprecated dependencies (Drupal 7/8, Akeneo v1.x), security vulnerabilities, and lack of maintenance. The bundle may break with updates to Akeneo or Drupal Commerce. Mitigate by isolating it in a Docker container, using API wrappers, or replacing it with a modern stack (e.g., Sylius + Akeneo API).
- Can I use this bundle for real-time product syncs, or is it batch-only?
- This bundle is batch-oriented (scheduled exports). For real-time syncs, you’d need to extend it with webhooks (Akeneo → Drupal) or use Laravel’s event-driven architecture (e.g., Laravel Queues) to poll Akeneo/Drupal APIs periodically. Consider GraphQL subscriptions for live updates.