Weave Code
At a glance
Frequently asked questions about Piivo Connector
- Can I use akeneo/piivo-connector directly in a Laravel 10+ project?
- No, this package is a Symfony bundle and isn’t natively compatible with Laravel. You’d need a microservice (e.g., Lumen) as a proxy or rewrite it into a Laravel package, which requires significant effort due to Symfony dependencies like AppKernel and routing.
- What Laravel versions does this package support?
- This package doesn’t support Laravel directly. If you’re using Laravel 8+, you’ll need a custom wrapper or microservice to bridge the Symfony bundle. Older Laravel versions (pre-8.x) might have slightly easier interoperability with Symfony, but it’s still not plug-and-play.
- How do I handle Elasticsearch conflicts with Laravel Scout or Algolia?
- The package modifies Elasticsearch indexes, which can clash with Laravel’s search stacks. Isolate the indexing logic by running PiiVO-specific searches in a microservice or replace Elasticsearch with Laravel Scout/Algolia by rewriting the metadata storage layer.
- Is there a step-by-step guide to integrate this with Laravel?
- No official guide exists. The recommended approach is to deploy a separate microservice (e.g., Lumen) that uses the Symfony bundle internally, then expose a REST/GraphQL API for Laravel to consume. This avoids direct Symfony-Laravel conflicts.
- What are the alternatives to akeneo/piivo-connector for Laravel?
- Consider Laravel-native DAM integrations like Cloudinary, Bynder, or custom packages for Akeneo’s official API. If you’re tied to PiiVO, a microservice proxy is the most practical workaround without rewriting the entire bundle.
- Does this package support Akeneo PIM v5+?
- The package was last updated in 2018 and targets Akeneo v2.x. Compatibility with Akeneo v5+ isn’t guaranteed. Test thoroughly or expect to patch gaps, especially if using modern Akeneo features like the API platform.
- How do I handle the AppKernel.php dependency in Laravel?
- Laravel doesn’t use AppKernel.php, so you’ll need to either fork the bundle and replace Symfony’s kernel logic with Laravel’s ServiceProvider or abstract the bundle into a microservice. This is a critical blocker for direct integration.
- Will this package work with PHP 8.2+?
- Unlikely without modifications. The package relies on older Symfony and PHP dependencies (e.g., PHP 7.1+). Update the bundle’s dependencies manually or use a microservice to isolate the legacy PHP environment.
- Can I use this package for production without a microservice?
- Only if you’re willing to accept high technical risk. Direct integration requires rewriting core Symfony logic (e.g., routing, service container) and may introduce instability. A microservice is the safer, scalable approach for production.
- How do I test this package in a Laravel environment?
- Test via a microservice first—deploy the Symfony bundle in a separate Lumen/Symfony app and mock API calls from Laravel using Guzzle or HTTP clients. This isolates Laravel-specific issues and validates the integration before full deployment.
Weaver
How can I help you explore Laravel packages today?