morningmedley / application

v0.4.9 2026-10-12 10:52 UTC

Requires

• php: ^8.2
• illuminate/cache: ^12.31.0
• illuminate/config: ^12.3.0
• illuminate/console: ^12.31.0
• illuminate/container: ^12.31.0
• illuminate/filesystem: ^12.31.0
• illuminate/http: ^12.31.0
• illuminate/log: ^12.31.0
• illuminate/support: ^12.31.0
• spatie/laravel-ignition: ^2.9.1
• symfony/finder: ^6|^7
• symfony/http-foundation: ^6|^7
• vlucas/phpdotenv: ^5.6.1

MIT

• Mathias Munk

• framework
• wordpress
• morningmedley

Published on Packagist.org on 2026-10-12 10:53 UTC

README

An Illuminate Application for Morningmedley.

Breaking changes since 0.4.8

• Nothing logs to a file by default. The debug channel and the WP_DEBUG_LOG path handling are removed, and the default stack is null. PHP and WordPress write the log file. A single channel (storage/logs/laravel.log) is defined, but it is not in the stack. A site that lists debug in its own channels.stack must change it, for example to bugsnag. With a channel that does not exist, Laravel falls back to the emergency logger, which now writes to php://stderr.
• app.debug is now WP_DEBUG && WP_DEBUG_DISPLAY, where 0.4.8 used WP_DEBUG && WP_DEBUG_LOG. It is what Laravel reads as "show details": error pages with the exception and its trace, the Laravel exception renderer, Ignition's runnable solutions, the health check and a missing Mix file, which throw instead of being reported. They now show details only when errors are displayed. app.debug_log is removed.
• HandleExceptions lost handleWarningError(), handleNoticeError() and handleDeprecationError(). handleError() covers every level.

Warnings, notices, deprecations, exceptions and fatal errors are reported to the channels in the stack, and a channel chooses which it gets with its level. Warnings, notices and deprecations are never thrown, and PHP and WordPress keep logging, displaying and ending the script on E_USER_ERROR. See the comment above the stack in src/config/logging.php.

Resources

• Documentation
• Contributing