Weave Code
Akeneo PIM Excel initialization bundle
Frequently asked questions about Excel Init Bundle
- Can I use akeneo/excel-init-bundle in a Laravel project instead of Symfony?
- No, this bundle is designed for Akeneo PIM, which is built on Symfony, not Laravel. To integrate it with Laravel, you’d need a custom bridge or rewrite components like the EventDispatcher for Laravel’s ecosystem. For Laravel, consider Akeneo’s REST API or CSV imports instead.
- What Akeneo PIM versions does this bundle support?
- The bundle has version-specific compatibility matrices. For example, `3.0.*` supports Akeneo PIM `>=3.0`, while `1.0.*` targets `v1.6.*`. Check the [README compatibility table](https://github.com/FriendsOfAkeneo/ExcelInitBundle) to confirm your Akeneo version is supported.
- Why does the bundle require Excel 2016+ and reject LibreOffice/OpenOffice files?
- The bundle relies on strict XLSX validation tied to Microsoft Excel’s schema. LibreOffice/OpenOffice may alter file structures, causing silent failures or corrupted Akeneo catalog data. Always use Excel 2016+ and avoid editing the `init.xlsx` template with non-Microsoft tools.
- How do I install and configure this bundle in Akeneo?
- Run `composer require akeneo/excel-init-bundle:3.0` (adjust version for your Akeneo PIM), enable the bundle in `AppKernel.php`, then warm the cache and install assets with `php bin/console cache:warmup --env=prod` and `php bin/console pim:installer:assets --env=prod`.
- Is there a template for non-technical users to create init.xlsx files?
- Yes, the bundle includes a `minimal/init.xlsx` template in its `src/Resources/fixtures` directory. This file defines the required sheets (families, channels, currencies) and structure. Users must adhere to this template to avoid import failures.
- What happens if I upgrade Akeneo PIM but this bundle isn’t maintained?
- Since the last release was in 2019, upgrading Akeneo PIM (e.g., to v6.x) may break compatibility. No active maintenance means you’ll need to either fork the bundle, patch it manually, or migrate to Akeneo’s native API or newer bundles like `akeneo/import-export`.
- Are there alternatives to this bundle for Excel imports in Akeneo?
- Yes, consider Akeneo’s native [REST API](https://docs.akeneo.com/) or the `akeneo/import-export` bundle for CSV/Excel imports. These are actively maintained and support modern Akeneo versions. The API also integrates better with Laravel via HTTP clients.
- How do I handle errors like mismatched channel names in the Excel file?
- The bundle provides basic validation, but errors (e.g., channel typos) may only surface during import. Check the `channels` and `family` sheets for consistency. For debugging, enable Akeneo’s debug mode (`APP_DEBUG=1`) and review the `var/log/prod.log` for detailed failure messages.
- Does this bundle support large-scale Excel imports (e.g., 100K+ products)?
- No, the bundle is optimized for initializing catalog *structure* (families, channels, currencies), not bulk product imports. For large datasets, use Akeneo’s API or the `akeneo/import-export` bundle, which supports batch processing and better performance.
- How can I test this bundle before production use?
- The bundle lacks unit tests, but you can validate functionality by testing with a small `init.xlsx` file in a staging Akeneo environment. Use the `pim:installer:assets` command to reset the catalog and retry imports. Monitor logs for errors and compare the imported structure against your template.
Weaver
How can I help you explore Laravel packages today?