Fix automatic redirects for Eloquent stored entries#601
Merged
Conversation
duncanmcclean
approved these changes
Jun 12, 2026
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
2 participants
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.
When collections/entries are stored in the db using the Eloquent driver, automatic redirects are not getting created when the slug changes.
Since the current
initialPath()check is a flat file agnostic, Eloquent entries are never loaded andinitialPath()is always null so the handler returns early before caching the original URL. The result is that no redirect gets created.This introduces a small helper that's storage-agnostic and resolve the previous slug to make automatic redirects work properly.