[5.x] Fallback to nocache
content when request is missing the Cache
middleware
#9406
+20
−1
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.
This pull request fixes an issue with the
{{ nocache }}
tag on custom routes that aren't using Statamic'sCache
middleware, used for static caching.Previously, if you used the
{{ nocache }}
tag or it's Blade directive counterpart on a custom route without the middleware,NOCACHE_PLACEHOLDER
text will have been displayed.This PR fixes that and simply falls back to the intended contents / view when the response isn't being statically cached.
Fixes #6744.