Flush rewrite rules at the end of each deploy#1567
Merged
swalkinshaw merged 1 commit intoroots:masterfrom Apr 12, 2025
joshuafredrickson:master
Merged
Flush rewrite rules at the end of each deploy#1567swalkinshaw merged 1 commit intoroots:masterfrom joshuafredrickson:master
swalkinshaw merged 1 commit intoroots:masterfrom
joshuafredrickson:master
Conversation
Member
|
Thank you! |
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.
Permalinks aren’t automatically flushed on deployment, so I usually handle it in a deploy hook. Since rewrites function like a cache—similar to Acorn, ACF, or Redis—it makes sense to clear them during deployment.
For example, adding a new CPT requires flushing rewrites manually for the archive page to work. Automating this would help ensure rewrites just work after deployment.