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
Controlling caching of block #486
Comments
Are you sure it's the block being cached and not the entire page? |
How do I tell if the page is being cached and not just the block? Other parts of the page such as in the header respect my turpentine configuration options, like the cart and log in / out links that are set to private. |
You could inspect the response headers of the document and check what value the Age header has. This will only work if you have debug headers active or your own IP defined in the magento debug IPs. |
I flushed the cache and then checked the age value, it is continually increasing so it looks like the page is being cached. Is there a way to un-cache the page? Would I then have to set caching options for all the blocks on the page individually? |
You could not cache the whole page by specifying
And from what I gather from the esi policy docs https://github.com/nexcess/magento-turpentine/wiki/ESI_Cache_Policy you could do the following to hole-punch just the block:
The above could work, but I haven't tried that myself. |
What @eth8505 suggested for not caching the contacts page, or for hole-punching should work. |
Mind that wholepunching the contactForm block ist not enough. The form action is only |
Hi, I have a contact-us page with a block containing the contact-us form. I want just this block to not be cached. Here is my contacts.xml:
I have tried every combination of settings in the EsiOptions I could find but I cannot get the block to stop caching. For testing purposes I have added a timer to my contact form template and no matter what I try it gets cached.
I have managed to stop caching a block that is in the default handle but I'm having no luck with this form.
Thank you
Anthony
The text was updated successfully, but these errors were encountered: