- Can I use this bundle in a Laravel project instead of Akeneo PIM?
- No, this bundle is designed exclusively for Akeneo PIM (Community/Enterprise) and relies on Doctrine ORM and Symfony bundle conventions. Porting to Laravel would require rewriting core logic, replacing Doctrine with Eloquent, and building custom frontend components. Evaluate alternatives like Spatie’s attribute packages if Laravel is your primary platform.
- What Laravel versions does this bundle support?
- This bundle does **not** support Laravel—it’s built for Akeneo PIM v2.x (Symfony-based). If you’re using Laravel, you’ll need to manually adapt the logic (e.g., Eloquent migrations, custom service providers) or seek Laravel-native alternatives. Check the README for Akeneo-specific version requirements.
- How do I add descriptions to existing attributes without data loss?
- For Akeneo, use the bundle’s import/export feature by adding `description-{locale_code}` columns (e.g., `description-en_US`) to your CSV files. Run imports via Akeneo’s standard workflow. For Laravel, you’d need to create a migration to add description fields to your attribute tables and backfill data manually or via API.
- Does this bundle work with custom Akeneo attribute types (e.g., pim_catalog_number)?
- The bundle overrides Akeneo’s `Attribute` and `AttributeTranslation` entities, which should work with most standard types. However, test thoroughly with custom types (e.g., `pim_catalog_number`) in a staging environment, as Doctrine schema updates (`doctrine:schema:update --force`) may cause conflicts. Refer to Akeneo’s documentation for type-specific quirks.
- How do I display attribute descriptions on the frontend in Akeneo?
- The bundle automatically renders descriptions under attribute fields in Akeneo’s default product templates. If you’re using a custom theme, override the product page template to include the new `description` field from the `AttributeTranslation` entity. For Laravel, you’d need to create a Blade component or API endpoint to fetch and display these descriptions.
- What’s the best way to handle multilingual descriptions in Laravel if I don’t use Akeneo?
- For Laravel, consider using packages like `spatie/laravel-translatable` to manage multilingual fields or `orchid/software` for admin UI extensions. Alternatively, design a custom solution with Eloquent relationships (e.g., a `description` pivot table with `locale` columns) and handle imports/exports via Laravel Excel or API responses.
- Will this bundle break after an Akeneo PIM update?
- Yes, this bundle is tightly coupled to Akeneo PIM v2.x and may break with major Akeneo updates. Test updates in a staging environment and check the bundle’s changelog for compatibility notes. For Laravel, avoid this dependency entirely—opt for version-agnostic solutions like custom Eloquent models or third-party packages.
- How do I test this bundle before deploying to production?
- For Akeneo, test in a staging environment by importing sample data with descriptions, verifying the UI tab appears, and checking exports. Run `doctrine:schema:update --force` cautiously—back up your database first. For Laravel, mock the bundle’s logic with a proof-of-concept (e.g., a custom migration + seed data) before full integration.
- Are there alternatives for adding attribute descriptions in Laravel?
- Yes. For simple descriptions, add a `description` column to your product/attribute tables and use Eloquent accessors. For multilingual support, use `spatie/laravel-translatable`. For admin UIs, extend Laravel Nova or Jetstream with custom fields. Avoid Akeneo-specific bundles unless you’re fully invested in the PIM ecosystem.
- How do I configure the bundle for Akeneo Enterprise Edition?
- Install version `1.1.*` of the bundle (compatible with Akeneo EE v2.x) via Composer, then register it in `AppKernel.php` as documented. No additional configuration is needed beyond the standard setup—Enterprise Edition support is included in the `1.1.*` branch. Always verify with your Akeneo EE version’s release notes for edge cases.