- How do I install ycs77/laravel-wizard in a Laravel application?
- Install the package with Composer using the ycs77/laravel-wizard package name, then follow the repository README for any required configuration or publishing steps. Confirm the package's supported Laravel and PHP versions before adding it to an existing application. Run your test suite after installation to verify routes and views integrate cleanly.
- Which Laravel and PHP versions are supported by ycs77/laravel-wizard v4.5.0?
- The provided release context does not list a specific Laravel and PHP support matrix for v4.5.0. Check the package's composer.json, README, and release tags for the authoritative constraints. Test the upgrade in a branch against your application's exact Laravel and PHP versions before production.
- How do I define multi-step wizard steps and validate each stage?
- Use the package's fluent API to define the wizard steps and attach validation to each stage. The wizard should allow navigation only after the current step's validation passes, keeping flow logic out of controllers and Blade views. Refer to the package source or README for the exact method names and validation syntax.
- Can laravel-wizard persist progress between steps?
- Yes, the package overview states that it can persist progress as users move through a wizard. The exact storage mechanism should be confirmed in the package documentation. Test resuming a partially completed wizard and still validate every step server-side rather than trusting persisted state alone.
- Does ycs77/laravel-wizard v4.5.0 support redirecting with parameters?
- Yes, v4.5.0 adds support for redirection with passing parameters, improving post-step navigation flexibility. The change is described as additive and scoped to redirection behavior. Verify whether your flow needs query strings, route parameters, or both by reviewing the package docs and source.
- Is upgrading to ycs77/laravel-wizard v4.5.0 a breaking change?
- The release note indicates no breaking changes, deprecations, or migration requirements for v4.5.0. Treat it as a minor-version upgrade: update Composer dependencies, run the application test suite, and add focused tests for wizard redirects with parameters. Validate in staging before releasing to production.
- Does laravel-wizard validate or sanitize redirect parameters?
- The provided context does not state whether the package validates or sanitizes redirect parameters itself. Treat destination validation and parameter allow-listing as application responsibilities unless the package documentation says otherwise. Add tests for encoding, preservation, and rejection of unexpected values.
- How do I prevent open redirects when wizard parameters influence redirect destinations?
- Do not let user-controlled parameters choose arbitrary destination URLs. Allow-list permitted routes or hosts, validate parameters before redirecting, and pass only opaque identifiers when possible. Also avoid exposing sensitive values in URLs, logs, or browser history.
- How should I test wizard redirects that pass parameters in Laravel?
- Write feature tests that complete or advance the wizard, assert the redirect response, and verify the expected parameters are preserved and encoded correctly. Include negative tests for invalid parameters and disallowed destinations. Run these tests in the same Laravel and PHP versions used in production.
- What are alternatives to laravel-wizard for multi-step forms in Laravel?
- Alternatives include building custom controllers and Blade views, using Livewire or Inertia wizard components, or adopting another Laravel form-flow package. Choose based on whether you need server-rendered Blade steps, per-stage validation, progress persistence, and redirect control. Evaluate maintenance activity and Laravel version support before switching.