Weave Code
Html Quickform2 Laravel Package
pear/html_quickform2
HTML_QuickForm2 is a PHP library for creating, validating, and rendering HTML forms, with server-side and client-side validation, multipage wizards, and pluggable elements and renderers.
HTML_QuickForm2 is a PHP library for creating, validating, and rendering HTML forms. A modern rewrite of PEAR HTML_QuickForm, it provides a fluent API built around pluggable elements, validation rules, and renderers.
- Supports all HTML4 form elements plus several custom elements
- Server-side and client-side validation, with rules combinable via
and/or - Multipage forms — tabbed forms and wizards
- Self-contained JS library, no framework dependency
- Pluggable elements, rules, renderers, and renderer plugins
Install with Composer: composer require pear/html_quickform2
Frequently asked questions about Html Quickform2
- What is pear/html_quickform2 and is it a Laravel package?
- PEAR HTML_QuickForm2 is a PHP library for creating, validating, and rendering HTML forms. It is not a Laravel package and ships no service provider, facade, config, or Laravel-specific integration. You can install it with Composer in a Laravel application, but you must wire it into controllers, views, validation, and security yourself.
- Does pear/html_quickform2 work with Laravel?
- It can be installed alongside Laravel and used inside controllers or services, but its procedural design does not integrate with Laravel's container, Blade, CSRF middleware, or Validator facade. Laravel's native FormRequest and Blade form components are usually the better architectural fit for new development. Using HTML_QuickForm2 in Laravel means owning bespoke bridge code.
- How do I install pear/html_quickform2 in a Laravel project?
- Install it with composer require pear/html_quickform2. Since release 2.1, Composer installation relies on autoloading and does not use require_once or include-path calls. There is no publishable configuration or service provider, so you instantiate HTML_QuickForm2 directly where needed.
- Is HTML_QuickForm2 compatible with PHP 8.5 and PHP 8.6?
- Version 2.5.0 adds clean PHP 8.5 and 8.6 runs, upgrades PHPUnit-Polyfills, and enables deprecation gating in GitHub CI. It also continues the PHP 8.4 compatibility work from v2.4.0. Pin to ^2.5 and treat the upgrade from 2.4.0 as low-risk and patch-equivalent.
- Can I use HTML_QuickForm2 validation with Laravel's Validator facade?
- No, there is no built-in integration with Laravel's Validator facade or FormRequest. HTML_QuickForm2 has its own server-side and client-side rules, including and/or combinations and common rules. You can manually map input and errors between the two systems, but that bridge is custom code you maintain.
- How do I handle CSRF protection and Blade escaping with HTML_QuickForm2 in Laravel?
- HTML_QuickForm2 does not provide built-in CSRF or XSS protection, so you must add Laravel's CSRF token and middleware manually. Rendering its raw HTML output in Blade typically requires wrapper views or output buffering. Output escaping and security handling remain your responsibility.
- Does HTML_QuickForm2 support multipage forms and custom elements?
- Yes, it supports multipage forms such as tabbed forms and wizards, plus custom elements, pluggable rules, and pluggable renderers. Client-side validation and JavaScript-backed elements use a small self-contained JS library with no JS framework dependency. HTML5 form element support is planned rather than complete.
- What are the best alternatives to HTML_QuickForm2 for Laravel forms?
- For Laravel applications, native FormRequest validation, Blade form components, and Laravel's validation rules are the most natural alternatives. Symfony Forms is an option outside Laravel, and Livewire or Inertia.js fit component-based interfaces. HTML_QuickForm2 remains a legacy PEAR-oriented choice rather than a Laravel-native one.
- Is pear/html_quickform2 abandoned or actively maintained?
- The prior abandoned characterization is no longer accurate because there were two 2025 releases and active CI maintenance. It is still a small PEAR-ecosystem project, so treat it as a single-vendor dependency. Abandonment risk is now low to medium, and future PHP compatibility regressions are more likely to be caught by its CI.
- How do I test HTML_QuickForm2 forms in a Laravel application?
- Use PHPUnit to test the form object's validation and rendering behavior directly. The package uses PHPUnit-Polyfills and CI deprecation checks, but it provides no Laravel testing helpers. Laravel HTTP tests can still post to routes that use the form, and you can assert rendered HTML and validation outcomes carefully.
Weaver
How can I help you explore Laravel packages today?