Weave Code
Form Error Log Bundle Laravel Package
lendable/form-error-log-bundle
A Symfony bundle that captures and logs form validation errors, so you can trace failed form submissions, debug validation issues, and monitor error patterns across your application.
Log form errors
Frequently asked questions about Form Error Log Bundle
- Does lendable/form-error-log-bundle work with Laravel?
- No. It is a Symfony bundle built around Symfony's dependency injection container, HttpKernel and FormEvents::POST_SUBMIT, so installing it in a Laravel app registers no service provider, facade or auto-discovery entry and executes nothing. Laravel's validation pipeline never reaches the bundle's event subscriber. The underlying idea is portable, but the package itself is not.
- Why doesn't the v2.0.0 release make this package Laravel-compatible?
- The v2.0.0 change moves autoloading from PSR-0 to PSR-4, which only affects how Composer resolves class names to file paths. It adds no service provider, no publishable config, no facade and no Laravel auto-discovery, and it does not boot the form subscriber outside Symfony's container. A major version tag is not evidence of Laravel support.
- How do I log Laravel form validation errors without adding a package?
- Override failedValidation() on a base FormRequest, or wrap the request in middleware that catches Illuminate\Validation\ValidationException around $next($request). Log the field path, the failed rule, the form or route name and a correlation ID. That is roughly 40 to 80 lines of code you own, and it needs no third-party dependency.
- Can Symfony bundles be installed in a Laravel application at all?
- Composer can download the code, but nothing wires it into the framework. Symfony bundles depend on Symfony's Kernel, DI container and event dispatcher, while Laravel ships its own container and request lifecycle. Without a bridge or adapter you write yourself, the bundle's services and subscribers are never invoked.
- Is lendable/form-error-log-bundle still maintained?
- That is unverified. Prior assessment recorded the repository as archived with a last release in November 2017, yet a v2.0.0 release exists, and no refreshed repository metadata was supplied. A PSR-4 migration is a mechanical packaging change, not evidence of PHP 8 fixes, current Symfony support, CI or a security policy. Treat it as effectively unmaintained until the full changelog, release date and supported version matrix are confirmed.
- Is it safe to log form validation error messages in production?
- Be careful. Symfony and Laravel both interpolate submitted values into validation messages, so logging raw messages can write user input such as emails or addresses into a lower-trust log system. Log the field path, rule and a correlation ID instead of the message body, or redact and hash values before they reach the log.
- What alternatives are there for logging form validation errors in Laravel?
- Build it natively: a base FormRequest or a small middleware that reports validation failures to a dedicated channel or a product-analytics event pipeline. For error tracking, Laravel's exception handler or services such as Sentry or Flare can capture ValidationException if you choose to report it. The native approach keeps ownership and avoids carrying a framework-specific dependency.
- What does lendable/form-error-log-bundle actually do?
- In Symfony it subscribes to form submission events, collects field-level validation error messages, and writes them to a configurable logging channel with contextual metadata. It gives teams visibility into failed submissions without exposing extra detail to end users. None of that machinery runs inside a Laravel application.
- How do I capture form validation errors for analytics rather than the application log?
- Dispatch a domain event, or push an event to your analytics pipeline, from failedValidation() or from the middleware that catches ValidationException. Include the form identifier, field path, failed rule, timestamp and a correlation ID, but exclude raw user input. Routing the signal to product analytics is usually more useful than writing it to a text log.
- Does the bundle support PHP 8 and current Symfony or Laravel versions?
- The supplied release note says nothing about the supported PHP or Symfony version matrix; the autoloading migration is silent on it. That constraint matrix has to be confirmed from the full v2.0.0 changelog and composer.json before any evaluation. Laravel support is not on the table regardless, because the package has no Laravel integration layer.
Weaver
How can I help you explore Laravel packages today?