- Can this bundle work with Laravel without Akeneo PIM?
- No, this bundle is exclusively designed for Akeneo PIM (3.x/4.x) and requires Akeneo as a dependency. If you’re using Laravel without Akeneo, you’d need to replicate its export logic or use alternative solutions like Spatie’s XML builder for custom XML generation.
- What Laravel versions does this bundle support?
- This bundle does not directly support Laravel—it’s built for Akeneo PIM. However, you could integrate Akeneo’s exports into Laravel via its REST API or by embedding Akeneo as a microservice. Laravel’s version compatibility isn’t a factor here.
- How do I handle media/image conflicts between Akeneo and Laravel’s storage?
- Akeneo copies images to `web/media`, which may conflict with Laravel’s default `storage/app/public`. Resolve this by configuring LiipImagine to use Laravel’s filesystem or symlinking `web/media` to `storage/app/public/media` (e.g., `ln -s storage/app/public/media public/web/media`).
- Are the validation levels (low/medium/high) customizable for Google Manufacturer?
- The bundle provides three validation tiers, but custom rules require extending Akeneo’s event system (e.g., `pim_enrichment_data_normalizer_post_set`). You can add Symfony Validator constraints or override the bundle’s logic in a child class for advanced use cases.
- Does this bundle support async or chunked exports for large product catalogs?
- No, the bundle uses synchronous XML generation with no built-in async or chunked export support. For large catalogs, consider processing exports in Akeneo’s batch jobs or integrating Laravel Queues to handle post-export tasks like API submissions.
- Will this bundle work with Akeneo PIM 5.x or future versions?
- The bundle is tested for Akeneo 3.x/4.x. Upgrades to Akeneo 5.x or later would require manual testing or contributions from Agence Dn'D, as the bundle isn’t actively maintained for future Akeneo versions. Check their GitHub for updates.
- Can I use this bundle to submit XML files directly to Google Manufacturer’s API?
- This bundle generates Google Manufacturer-compliant XML files but does not include logic for submitting them to Google’s API. You’d need to handle API calls separately, possibly using Laravel’s HTTP client or a queue job for retries.
- How do I handle failed exports or retries in production?
- Failed exports are managed via Akeneo’s native job system. For Laravel integration, you’d need to log export statuses (e.g., via Laravel Log) and implement custom retry logic using Laravel Queues or cron jobs to reprocess failed batches.
- Are there alternatives for Laravel-only Google Manufacturer exports?
- Yes, if you’re not using Akeneo, consider alternatives like Spatie’s XML builder for custom XML generation, or packages like `spatie/array-to-xml` to structure data. For full Google Merchant Center integration, explore Laravel packages like `spatie/google-merchant-center`.
- How do I map custom Akeneo attributes to Google Manufacturer’s optional fields?
- Use Akeneo’s export profile UI to map Akeneo attributes to Google Manufacturer’s optional fields (e.g., `feature_description`, `additional_image_link`). The bundle provides a dedicated section for configuring these mappings during profile creation.