-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
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
caching docs is confusing and missing important info #54
Comments
You shouldn't have to do that - the |
@dwightwatson I know the render() does that.. I noticed However I don't understand the thinking behind this since the call to Sitemap::render() is usually done after doing all the processing. My controller action for one of my sitemaps (a big one with 5k url and 10k images, does a huge amount of processing in order to build up the sitemap. How is having a check for a cached version at the bottom of that code allowing to skip the processing.. which is the point of caching. Maybe there's something I'm not getting? Here's my code
|
Yeah... that's actually a very fair point. Will re-open this as to address the documentation on this area better. Open to PRs on it otherwise I'll try and find some time to improve this soon. |
Took me a while to figure out how the cache works and had to read a lot of issues and look into the code to finally get to the conclusion that on top of enabling the cache in the config file, you must add this code at the top of your controller action to return the cached version
The text was updated successfully, but these errors were encountered: