Weave Code
Ezworkflowenginebundle Laravel Package
kaliop/ezworkflowenginebundle
A Symfony bundle that adds a configurable workflow engine to eZ Platform and eZ Publish. Define states, transitions, triggers, and actions in YAML to automate editorial and content publishing processes, with support for custom workflow services.
Kaliop eZ-Workflow-Engine Bundle
Frequently asked questions about Ezworkflowenginebundle
- Is kaliop/ezworkflowenginebundle a Laravel package?
- No. It is a Symfony bundle built for eZ Publish 5 and eZ Platform, now Ibexa, and it relies on the eZ kernel, repository APIs, event dispatcher, and service container conventions. It does not provide Laravel service providers or Artisan commands, so it is not a drop-in package for Laravel applications.
- Can I install kaliop/ezworkflowenginebundle in a Laravel app with Composer?
- Direct composer require into a Laravel app is not viable in practice. The dependency graph pulls in eZ/Ibexa kernel packages that conflict with Laravel's Symfony component constraints and framework assumptions. You would need to isolate Ibexa as a separate service or reimplement the workflow semantics on Laravel-native tooling.
- What is kaliop/ezworkflowenginebundle used for?
- It adds a configurable workflow engine to eZ Publish and eZ Platform for modeling and automating content lifecycle processes. Developers define states, transitions, triggers, and actions in configuration, then trigger automatic actions on content publish, update, or deletion. It is aimed at editorial and approval processes inside an eZ or Ibexa estate.
- How do I configure workflows in YAML with this bundle?
- Workflows and transitions are defined in Symfony and eZ bundle configuration, typically YAML, and wired through the eZ and Symfony service container. The bundle maps content events to workflow triggers and lets you attach actions or custom workflow handlers. Exact keys depend on the bundle version, so validate against the repository documentation and the installed 2.1.0 release.
- Does this bundle support Laravel 10 or Laravel 11?
- No supported Laravel version is claimed, and the architecture does not target Laravel. It is a Symfony bundle for eZ Publish 5, eZ Platform, and Ibexa, not a Laravel package with Laravel service providers or Artisan commands. For Laravel 10 or 11, use symfony/workflow with Laravel events and queues or a lightweight custom state machine instead.
- How do I test workflows built with kaliop/ezworkflowenginebundle?
- Testing should run inside an eZ Platform or Ibexa application kernel where the bundle services, content repository APIs, and event dispatcher are available. Use the CLI debug commands, including kaliop:workflows:debug --show-path, to inspect transition reachability before writing integration tests. Unit-testing the YAML semantics in isolation is possible only if you extract or reimplement the definition model.
- What are the production risks of using this bundle?
- The main risks are platform coupling, low downstream validation, and licensing. The repository has about 7 stars and 0 dependents, and although 2.1.0 shows the maintainer is still shipping, it remains a single-maintainer project on a deprecated platform. Internal service signatures have also changed, so forking and maintaining it carries ongoing upgrade cost.
- Is kaliop/ezworkflowenginebundle GPL licensed, and can I use it commercially?
- It is GPL-2.0, a strong copyleft license. Distributing a product that incorporates or derives from the code can trigger source-disclosure obligations for the derived work, so internal-only use is generally safer but must be confirmed by counsel. Do not copy, port, or vendor the code into a commercial Laravel product without legal review.
- What alternatives should I consider for Laravel workflow automation?
- For Laravel, symfony/workflow combined with Laravel events, queues, and notifications covers most state-machine and approval-chain needs. A lightweight custom state machine is also reasonable when the workflow is small and content lifecycle hooks map cleanly to Eloquent model events. If you specifically need Ibexa compatibility, run Ibexa as a separate bounded-context service and integrate over HTTP or a message bus.
- Is kaliop/ezworkflowenginebundle maintained and safe to fork?
- It is low-activity rather than clearly abandoned, because release 2.1.0 shows the maintainer is still shipping Symfony Console command enhancements. However, 7 stars and 0 dependents mean there is no downstream validation, and the recent refactor of WorflowServiceInner::executeMigration keeps the old signature working while deprecating it. That internal API movement is a warning that fork-and-maintain costs are real.
Weaver
How can I help you explore Laravel packages today?