Weave Code
Akeneo PIM developper toolbox
Frequently asked questions about Dev Toolbox Bundle
- Can I use Akeneo DevToolboxBundle in a modern Laravel 8+ project?
- No, this bundle is designed for Akeneo PIM (Symfony 2.x) and lacks Laravel compatibility. It requires manual AppKernel.php registration, which is deprecated in Laravel. For Laravel, consider wrapping its logic in custom Artisan commands or using Akeneo’s official API instead.
- What Laravel versions does this bundle support?
- This bundle does not natively support Laravel. It’s built for Symfony 2.x and Akeneo PIM Community Dev ~1.3 (2016-era). Attempting to use it in Laravel 5+ will likely fail due to architectural mismatches, including Doctrine and CLI integration differences.
- How do I install DevToolboxBundle in an Akeneo PIM project?
- Add the VCS repository to your `composer.json`, require the package via `composer require akeneo-labs/dev-toolbox-bundle`, then register the bundle in `app/AppKernel.php`. Note: This requires Akeneo PIM Community Dev ~1.3 and Symfony 2.x, not modern Akeneo (6+/7+) or Laravel.
- Does this bundle work with Akeneo PIM 6.x or 7.x?
- No, this bundle is locked to Akeneo PIM Community Dev ~1.3 and will not work with newer versions (6.x/7.x). Akeneo’s architecture changed significantly post-1.3, so migration would require extensive refactoring or a custom fork. Check Akeneo’s official documentation for modern alternatives.
- What commands does DevToolboxBundle provide, and are they useful for Laravel?
- The bundle offers CLI commands for deleting attributes and changing their scope in Akeneo PIM. These are Akeneo-specific and not applicable to Laravel unless you’re integrating with Akeneo’s legacy backend. For Laravel, consider Laravel Scout, Eloquent events, or custom Artisan commands for similar functionality.
- Is there any documentation or testing for this bundle?
- The bundle includes basic README documentation for its commands (attribute deletion/scope changes), but there’s no visible test suite, CI/CD pipeline, or maintainer activity. Use it cautiously in production, especially since it lacks regression testing and modern compatibility guarantees.
- Can I use this bundle in a non-Akeneo Laravel project?
- No, this bundle is tightly coupled to Akeneo PIM’s Doctrine entities and Symfony 2.x services. It won’t work in a vanilla Laravel project. If you need attribute management tools, explore Laravel packages like `spatie/laravel-activitylog` or build custom Artisan commands using Eloquent.
- What PHP versions does DevToolboxBundle support?
- The bundle likely supports PHP 5.6–7.0, aligning with Akeneo PIM Community Dev ~1.3’s requirements. Modern Laravel projects require PHP 8.0+, so this bundle is incompatible unless you’re maintaining a legacy Akeneo 1.3 environment.
- Are there alternatives to DevToolboxBundle for Akeneo PIM development?
- For modern Akeneo PIM (6.x/7.x), use Akeneo’s official API or CLI tools. For legacy Akeneo 1.3, consider forking this bundle or writing custom Symfony Console commands. If you’re using Laravel with Akeneo, integrate via Akeneo’s REST API or build Laravel-specific tools instead of relying on this bundle.
- How do I handle licensing conflicts with OSL-3.0 in my Laravel project?
- OSL-3.0 is an open-source license, but ensure it aligns with your project’s license (e.g., MIT, GPL). If using this bundle in a Laravel project, isolate it in a separate Composer package or vendor directory to minimize licensing risks. Consult a legal expert if unsure about compatibility.
Weaver
How can I help you explore Laravel packages today?