[6.x] Replace system status with maintenance mode - #19513
Merged
Conversation
Contributor
📚 Storybook previews@craftcms/ui — open Storybook Changed components: resources/js — open Storybook No changed components detected in this Storybook. |
riasvdv
marked this pull request as ready for review
August 31, 2026 09:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Completely replace Craft system status with Laravel maintenance mode. We already partly had this before but we still had the
system.livestatus as well, this completely removessystem.livein favor of purely Laravel's maintenance mode.I've tried to do this without needing to override Laravel's default middleware, but our logic was a bit too specific for this. Replacing the built-in middleware is very rare to do in a Laravel project, so running into an issue with a host app replacing it won't happen often, if at all.
I've also audited all 5.x routes that were allowed when the system was offline, which surfaced a few I missed before.
Adds
Route::allowDuringMaintenance()to the route registration, so allowing routes is more straightforward and doesn't separate the excluding (which was inRouteServiceProviderbefore) from the route registration. The middleware now gathers all routes with that exclusion metadata.This uses Laravel's new route metadata feature so the Laravel requirement has bumped to 13.17