We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just experimenting with the @nocache directive for a new project.
I have a header that contains auth-based items (e.g. settings / profile) so I am using the nocache directive like so: @nocache('partials.nav-main')
@nocache('partials.nav-main')
But all I am seeing is: NOCACHE_PLACEHOLDER
NOCACHE_PLACEHOLDER
The layout is a blade component but I have also tried it with a layout that uses template inheritance. Same results either way.
Try the @nocache directive in blade.
No response
Version: 3.3.34 PRO Laravel Version: 9.28.0 PHP Version: 8.1.1
Fresh statamic/statamic site via CLI
The text was updated successfully, but these errors were encountered:
Is this on a custom route?
Sorry, something went wrong.
It is indeed! My apologies, I get it now.
I guess it's a case of adding the statamic.web middleware to my custom routes. ->middleware(['statamic.web']);
->middleware(['statamic.web']);
@nocache
No branches or pull requests
Bug description
Just experimenting with the @nocache directive for a new project.
I have a header that contains auth-based items (e.g. settings / profile) so I am using the nocache directive like so:
@nocache('partials.nav-main')
But all I am seeing is:
NOCACHE_PLACEHOLDER
The layout is a blade component but I have also tried it with a layout that uses template inheritance. Same results either way.
How to reproduce
Try the @nocache directive in blade.
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
No response
Additional details
No response
The text was updated successfully, but these errors were encountered: