v2.1.0

Features

• codes from env: error-pages.codes also accepts a comma-separated string or a single integer, e.g. 'codes' => env('ERROR_PAGES_CODES') with ERROR_PAGES_CODES=403,404.
• TALLKit page: the action button follows the same rules as the fallback page (none on 503, login on 401 when the login route exists, back on 419, home otherwise) instead of TALLKit's "Go back home", with the right <html lang> and <title>.
• Fallback page: noindex meta, so error pages stay out of search results.
• Laravel Boost: the package ships a guideline in resources/boost/guidelines.

Fixes

• An untranslated locale uses the app's fallback_locale copy before English, and <html lang> matches the language of the copy.
• A status code missing from the chosen locale uses that locale's default copy instead of mixing languages; a null fallback locale no longer breaks the page.
• An invalid codes value no longer throws a TypeError.
• Custom exception handlers without a renderable() method no longer break the boot.
• symfony/http-kernel is now a declared dependency.

Copy changes

• The 419 description asks to go back instead of refreshing (en and pt_BR).
• The pt_BR 401 title reads "Entre para continuar".

Upgrading

composer update datalogix/laravel-error-pages

There are no breaking changes. If you published the language files (--tag=error-pages-lang), update the 419 description and the pt_BR 401 title in lang/vendor/error-pages by hand, or publish them again with --force.

Only the app's errors/{code}.blade.php replaces the package page; errors/4xx and errors/5xx are not considered.

What's Changed

• feat: review tooling, CI v2, locale fixes and TALLKit page by @ricardogobbosouza in #4

Full Changelog: v2.0.0...v2.1.0

v2.0.0

Breaking Changes

• Laravel 11 is no longer supported. The package now requires Laravel 12 or 13. Laravel 11 is end-of-life; applications still on it can keep using ^1.1, Composer won't offer them v2.

There are no code or behavior changes compared to v1.1.0.

Upgrading

composer require datalogix/laravel-error-pages:^2.0

What's Changed

• v2: drop Laravel 11, use workflows v1 and remove StyleCI by @ricardogobbosouza in #2

Full Changelog: v1.1.0...v2.0.0

v1.1.0

Highlights

• Context-aware action button: 401 links to your login route (when defined), 419 sends the user back to the previous page, 503 (maintenance) shows no button, and everything else links to the home page.
• show_exception_message option (default false): shows the message passed to abort(403, '...') instead of the translated description.
• TALLKit render failures no longer break the error page: if the TALLKit view throws (missing Vite manifest, unavailable database, …), the failure is reported and the dependency-free fallback page is rendered.

Fixes

• Unmapped status codes (405, 410, 422, …) no longer say "We couldn't find that page": 404 now has its own copy and default is generic.
• An untranslated locale (with an untranslated fallback locale) no longer turns every HTTP error into a bare 500; the bundled English copy is used instead.
• TALLKit is detected with providerIsLoaded() instead of class_exists(), so an installed but unregistered TALLKit no longer breaks rendering.
• Config is read at render time, so runtime config()->set() calls are respected.
• Copy fixes for 419 and 500 (en and pt_BR).

Important

Behavior change: an application's own resources/views/errors/{code}.blade.php now takes precedence over the package page for that status code. Previously the package silently shadowed it.

Note

If you published the language files, the new 404, go_back and sign_in keys are picked up from the package automatically. Your published default entry still holds the old "page not found" copy — update it if you want the new generic text.

What's Changed

• Improve error page robustness and consistency by @ricardogobbosouza in #1

Full Changelog: v1.0.0...v1.1.0

v1.0.0

First release