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
checkout_onepage_progress showing previous users shipping address #455
Comments
Add checkout/ to your URL blacklist in turpentine’s settings. |
Thanks, can be closed now. I thought this might be an issue but checkout_onepage_progress is specifically set in turpentine_esi.xml to not be cached? |
Interesting actually, the admin panel is exclusively defined to not cache it, even though while I was testing the admin panel in a non secure environment, varnish was definitely caching it. Which is why I added the URL to the blacklist which solved the problem. This perhaps could be an issue? |
@craigcarnell Sounds like there is a bug causing the nocache flag to be ignored, will investigate. @mytuxedo This is probably a different issue, as the admin panel is blacklisted with the same mechanic as the URL blacklist. Are you using a non-standard admin location (i.e. not |
@aheadley sorry was on another github account, I am indeed, it's set in etc/local.xml via:
|
@evensisftw Ok, can you run this script from your Magento root directory and paste the output here? <?php
define('MAGENTO_ROOT', getcwd());
include_once 'app/Mage.php';
var_dump( array(
Mage::getStoreConfig( 'admin/url/use_custom_path' ),
Mage::getStoreConfig( 'admin/url/custom_path' ),
Mage::getConfig()->getNode( 'admin/routers/adminhtml/args/frontName' ),
) ); EDIT: Updated script with an extra line. |
|
Very strange, |
FYI I installed a self signed certificate and used HTTPS and it was still caching the block. Appreciate your effort. Thanks! |
I just had exactly the same issue on Magento 1.9.2.4 with Turpentine 0.7.2. Although adding
|
Not sure if this is related to turpentine or not, but I am testing checkout (no HTTPS) and some of my users who are testing it are seeing a previous users shipping address in the checkout progress block?
We are using an external module to remove the postage step, but I have disabled it for now (only in it's admin setting):
Clearandfizzy_Reducedcheckout
The text was updated successfully, but these errors were encountered: