Weave Code
Pageflower Bundle Laravel Package
phpmentors/pageflower-bundle
A Symfony bundle from PHP Mentors that integrates Pageflower into Symfony applications. It supplies bundle configuration and service wiring for Pageflower's page-oriented features, helping developers add consistent page handling and navigation to PHP projects.
A pageflow engine for Symfony applications
Frequently asked questions about Pageflower Bundle
- Can I use phpmentors/pageflower-bundle in a Laravel application?
- No. PageflowerBundle is a Symfony bundle, not a Laravel package. It relies on Symfony bundle conventions, the DependencyInjection container, routing, forms, and session wiring. Laravel teams should not expect it to provide service providers or middleware.
- What is PageflowerBundle used for?
- PageflowerBundle integrates Pageflower, a lightweight page-flow framework, into Symfony applications. It is intended for multi-step forms, checkout flows, questionnaires, wizards, and similar explicit page journeys. It connects annotation-declared page transitions with Symfony's DependencyInjection container, routing, and Form components.
- How do I install phpmentors/pageflower-bundle?
- Install it with Composer using phpmentors/pageflower-bundle, then register the bundle in your Symfony kernel and add the required configuration and routes. Follow the bundle's documentation for service wiring and page-flow definitions. Before installing, confirm that its Composer constraints match your Symfony and PHP versions.
- Which Symfony and PHP versions does PageflowerBundle support?
- The available context only notes that v1.5.0 supports the new session service definition on Symfony 3.4.3 or later. It does not demonstrate support for Symfony 6 or 7, or for PHP 8.x. Check the package's composer.json constraints and run tests on your target runtime before relying on it.
- Does PageflowerBundle work with Symfony 6 or Symfony 7?
- There is no clear evidence that PageflowerBundle supports Symfony 6 or Symfony 7. The v1.5.0 release notes reference Symfony 3.4.3 session service behavior and older Symfony conventions. Treat modern Symfony support as unproven until the package constraints and tests show otherwise, and expect that a fork or port might be needed.
- How does PageflowerBundle handle form validation between steps?
- PageflowerBundle includes form-flow support for validating each step before advancing to the next page. Page-flow storage and transition handling are configurable, so you can adapt some behavior to your application. You should still define and test your own transition guards, authorization rules, and persistence expectations.
- Is PageflowerBundle actively maintained?
- The v1.5.0 release shows some maintainer activity, which is a positive signal compared with a 2020-only release history. However, the package has very low public adoption, with 5 stars and 0 dependents in the provided assessment. Treat it as a low-adoption dependency and plan for fork ownership or replacement if the workflow is business-critical.
- What are alternatives to PageflowerBundle for multi-step workflows in Laravel?
- For Laravel, use Laravel-native service providers, middleware, policies, events, and a workflow or state-machine library, or build a small page-flow abstraction. The Symfony Workflow component is an option in Symfony applications, but it is not a drop-in Laravel bundle. PageflowerBundle is more useful to Laravel teams as a reference implementation than as a dependency.
- What risks should I consider before using PageflowerBundle in production?
- Key risks include low adoption, unclear test coverage, undocumented compatibility limits, coupling to legacy Symfony APIs, and unclear persistence or session behavior. The security posture around transition guards and access control is also unknown from the provided context. Because v1.5.0 touches session service wiring and Request parameter handling, regression-test those areas carefully and isolate the engine behind an internal interface.
- Can I bridge PageflowerBundle into Laravel with an adapter?
- A bridge is technically possible but has low-to-moderate feasibility and is often not cost-effective. It would require running Symfony components alongside Laravel or wrapping bundle-specific services behind adapters. A cleaner approach is to extract the page-flow concepts into Laravel-native code and keep the Symfony bundle out of your runtime.
Weaver
How can I help you explore Laravel packages today?