humble-guys / humble-core

0.2.2 2026-09-28 12:36 UTC

Requires

• php: ^8.3
• filp/whoops: ^2.14
• guzzlehttp/guzzle: ^7.4
• illuminate/cache: ^10.43
• illuminate/config: ^10.43
• illuminate/console: ^10.43
• illuminate/container: ^10.43
• illuminate/contracts: ^10.43
• illuminate/database: ^10.43
• illuminate/events: ^10.43
• illuminate/filesystem: ^10.43
• illuminate/http: ^10.43
• illuminate/log: ^10.43
• illuminate/support: ^10.43
• illuminate/translation: ^10.43
• illuminate/validation: ^10.43
• illuminate/view: ^10.43
• league/flysystem: ^3.24
• ramsey/uuid: ^4.4
• roots/wp-password-bcrypt: ^1.1
• symfony/var-dumper: ^6.1
• vinkla/extended-acf: ^14.0
• vlucas/phpdotenv: ^5.4

Requires (Dev)

• laravel/pint: ^1.16
• pestphp/pest: ^2.36
• php-stubs/acf-pro-stubs: ^6.3
• php-stubs/wordpress-stubs: ^6.6
• phpstan/phpstan: ^2.2

proprietary

• Kim Larsson

Published on Packagist.org on 2026-09-28 12:37 UTC

README

humble-core

WordPress 404 routes

Register a custom not-found page using Route::wp('404', $handler). When no WordPress route matches, the router sets the main query to 404, sends the 404 status and no-cache headers, and resolves this registered route. If no 404 route is registered, it returns a plain Not Found response with status 404.

Controller and rendering exceptions still go through the server-error handler.