Weave Code
Classification Rule Bundle Laravel Package
akeneo-labs/classification-rule-bundle
Rules engine based automatic classification bundle
Frequently asked questions about Classification Rule Bundle
- Can I use this bundle with Akeneo PIM Community Edition instead of Enterprise?
- No, this bundle is designed exclusively for Akeneo PIM Enterprise (v1.3–1.6). The Community Edition lacks the required `CatalogRuleBundle` dependency, so direct integration is impossible without significant refactoring or forking.
- What Laravel applications can use this bundle?
- This bundle is not compatible with Laravel. It’s a Symfony2 bundle for Akeneo PIM Enterprise, which is built on Symfony2. If you need similar functionality in Laravel, you’d need to adapt the rule engine logic manually or explore Laravel-compatible alternatives like custom rule processors.
- How do I install and enable this bundle in Akeneo?
- Run `composer require akeneo-labs/classification-rule-bundle:1.2.*`, enable it in `AppKernel.php` under `registerBundles`, then clear the cache with `php app/console cache:clear --env=prod` and reinstall assets with `php app/console pim:installer:assets --env=prod`.
- What Akeneo versions does this bundle support?
- The bundle supports Akeneo PIM Enterprise versions 1.3–1.6. Version 1.2.* works with Akeneo >=1.6, while earlier versions (1.1.*, 1.0.*, 0.1.*) target specific older releases. Upgrading Akeneo beyond 1.6 may break compatibility.
- How do I define rules to unclassify products?
- Rules are defined in YAML format, extending Akeneo’s `CatalogRuleBundle`. Use the `unclassify` action to remove products from categories. For example, set the category code to `null` to fully declassify a product, or specify a category tree to target specific branches.
- Will this bundle work with modern Akeneo (v5+) or Symfony 5/6?
- No, this bundle is obsolete for Akeneo v5+ and Symfony 5/6. It relies on deprecated Symfony2 conventions and Akeneo v1.x APIs. Integration would require forking, patching, or building a custom adapter, which may not be feasible due to architectural changes.
- Are there alternatives for dynamic product classification in Laravel?
- For Laravel, consider packages like `spatie/laravel-activitylog` for auditing or custom rule engines built with Laravel’s service container. Alternatively, explore `spatie/laravel-medialibrary` for media-based categorization or `orchid/platform` for rule-driven workflows.
- How do I test rule configurations before deploying to production?
- Test rules in a staging environment by running them against a subset of products. Use Akeneo’s built-in rule validation tools or write custom unit tests to verify conditions and actions. Monitor logs for errors, especially when using `unclassify` on large product sets.
- What are the risks of using this outdated bundle in production?
- The bundle hasn’t been updated since 2016, so it carries risks like dependency conflicts, security vulnerabilities, and incompatibility with newer Akeneo versions. Rule misconfigurations could also break product categorization, leading to data inconsistencies or workflow disruptions.
- Can I extract the rule engine logic from this bundle for a custom Laravel solution?
- Yes, you could study the bundle’s rule evaluation logic (e.g., conditions/actions) and adapt it for Laravel. Focus on the core `unclassify` action and condition checks, then rebuild it using Laravel’s service providers, events, or task scheduling for batch processing.
Weaver
How can I help you explore Laravel packages today?