- Can I use shark/formlogger-bundle in a Laravel application?
- No. Shark FormLogger is a Symfony bundle tied to Symfony's HttpKernel, dependency injection container, and Form component. It has no Laravel service provider, facade, package discovery, or publishable config. Using it would mean running Symfony components alongside Illuminate, which is not a defensible design for a logging feature.
- How does Shark FormLogger capture form submissions in Symfony?
- It registers a form event listener and subscribes to Symfony Form events, most likely POST_SUBMIT, to capture submitted data and validation errors. The listener serializes the form data and error iterator and passes it to the configured logging driver. Controllers do not need changes.
- Does shark/formlogger-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony 2 and does not declare Laravel support. Symfony 2 reached end of life in 2019, and the bundle predates modern Laravel package conventions such as auto-discovery and publishable configuration. There is no tested or supported path for Laravel 10 or 11.
- What is the Laravel equivalent of Shark FormLogger?
- The Laravel-native equivalent is a small listener or exception-handler hook that catches ValidationException, plus a dedicated log channel with a JSON formatter. You can also log from a base FormRequest or a trait when validation fails. For debugging, Telescope or Sentry may be a better fit than a custom form logger.
- Is shark/formlogger-bundle safe for production use?
- It is not a good production dependency for a Laravel stack. The bundle is low-adoption, Symfony 2-era, and has no visible security-response process. Its core purpose is persisting raw form values and error messages, which creates a PII and secret-exposure risk unless redaction is added.
- How do I log Laravel form validation failures without a package?
- Catch Illuminate\Validation\ValidationException in your exception handler or override failedValidation in a FormRequest. Emit a structured array of field names and error messages to a dedicated log channel. Use an explicit allowlist and redact passwords, tokens, and payment or health fields before writing.
- Does shark/formlogger-bundle redact passwords and sensitive fields?
- There is no evidence in the package context that it redacts sensitive values by default. The described purpose is recording submitted form data and errors, which can include passwords, tokens, card numbers, and health data. Any adoption would require a strict field allowlist and redaction policy before logging.
- What are the alternatives to shark/formlogger-bundle for Laravel?
- For audit trails, use a database audit table rather than log files. For error-rate visibility, use Laravel's log channel with a ValidationException listener. For debugging, use Laravel Telescope or Sentry. A native implementation is usually tens of lines of code.
- How do I install and configure shark/formlogger-bundle?
- In a Symfony 2 application you would require it with Composer, enable the bundle in AppKernel, and configure its logging driver and ignored fields. The bundle is not installable as a normal Laravel package and has no service provider. For Laravel, treat installation as not applicable.
- Is shark/formlogger-bundle maintained and PHP 8.2 compatible?
- The package shows very low adoption, around 10 stars and no dependents, which suggests limited maintenance. Symfony 2-era bundles often declare php >=5.3 with no upper bound and may not be PHP 8.2+ compatible without patches. You would effectively own a fork if you adopted it.