Plugin Support
Kush
(@kushnamdev)
Hi @mrkingid,
Thank you for contacting us and for using our products. I’m sorry to hear about the difficulties you’ve encountered, and I’d be happy to assist you in resolving them.
I checked both sites, but the second one — https://artfulminds.ca/ — doesn’t load for me. So, based on my observation of the first one: if you’re seeing a BYPASS status, it usually means that the pages are either excluded from caching or you’re viewing them while logged in. Please confirm the status of the page using an incognito/private browser window where you’re not logged in.
When I checked in an incognito tab, I observed a DYNAMIC cache status instead of HIT, which can be easily addressed by following the steps below:
- Open the Super Page Cache plugin settings.
- Go to the Advanced tab.
- Enable the option: “Strip response cookies on pages that should be cached.”
- Save the settings and purge the cache.
This should resolve the issue. Let me know how it goes or if you need further help.
Best regards,
Thanks Kush, I did as you suggested but it is still showing as BYPASS when reviewing in incognito mode.
Plugin Support
Kush
(@kushnamdev)
could you please share the list of cookies you have in this option – https://vertis.d.pr/i/jPDdnT
Just the default. Nothing added on both sites.
comment_
woocommerce_
wordpress
xf_
edd_
jetpack
yith_wcwl_session_
yith_wrvp_
wpsc_
ecwid
ec_
bookly
Plugin Support
Kush
(@kushnamdev)
Hi @mrkingid,
I have checked your site’s header information and it shows cache control header value as private which should be the reason why it is not being cached properly. This could be affected due to other plugins you may have. Please try to enable this option – Overwrite the cache-control header for WordPress's pages using web server rulesThis forces SPC to apply the proper headers for public caching.
Also, please Deactivate any other caching plugin you may have and check again to see if the issue gets fixed or not. Make sure to purge all caches after saving changes.
Best regards
OK, figured it out with that last reply of yours. Checking the box didn’t work but…
I use WP Optimize and while I do not have the cache on my htaccess file has conditions written in it for WP Optimize. Taking all those references out of the htaccess file fixed the issue and I do not have to have either of the boxes ticked that you previously mentioned.
Goes to show you that just because you think something is OFF doesn’t mean it did something at some point.
Thanks for you help!
Plugin Support
Kush
(@kushnamdev)
Hi @mrkingid,
Thank you for the update, and I’m really glad to hear you were able to pinpoint the cause and resolve the issue!
You’re absolutely right—sometimes configurations or optimizations made in the past (even when disabled) can still leave residual impact, like in this case with the .htaccess entries from WP Optimize. It’s a great insight and will definitely help others facing similar behavior.
If anything else comes up or you need further assistance, feel free to reach out anytime. I’m happy to help.
Best regards,
