In Breeze I now have purge-cache set to 60 (it was 1440) and I’ve always had the “Add Expires” setting on.
In looking at Google Developer Tools I can see the Response Expires is set to one month out. Right now it is March 5th and the Expires is set to April 4th… 30 days later.
I believe this is what is impacting my users from getting the latest website articles on my homepage as the browser is being told “dont request latest html for another month”
EDIT: interestingly the Cloudways support page on browser caching shows browser cache settings for Breeze and W3 Cache. The breeze is a simple “on/off” where as W3 Cache offers a value field to set the expires amount. Why doenst breeze also offer that? How do I manage the browser expire timeframe in breeze... when W3 clearly has a value directly in their admin?
]]>I am about to buy pro version, in order to modifiy website and pushed on production new version.
After that i won’t need the plugin any more, what will happen to my pushed new site once license exoires o uninstall plugin?
THANKS
]]>1. Some Subscriptions that have been cancelled are still listed on the woocommerce dashboard under ‘cancelled’, but some are ‘not found’ or ‘Expired’ Can I ask what the difference is, please? I have not manually cancelled any Subscriptions.
2. Many Memberships are listed as ‘Expired’, but I only offer ongoing membership and recurring monthly subscriptions on my site, so what does ‘Expired’ mean here, if it isn’t that a fixed term membership ended? I have not manually cancelled any Memberships.
3. Some customers have an ‘Active’ Subscription linked to an ‘Expired’ Membership. What does this mean? I thought you needed a Membership in order to have a Subscription? How would they log in without a Membership?
4. Many Memberships have their ‘Last Login’ listed as *after* the date it says their Membership expired. Again, what does this mean? How would they log in without a Membership?
Thank you,
Marcus
Thousandfacesfilms.com
]]>Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status, x-litespeed-cache, x-lsadc-cache, x-qc-cache.
cache-control, expires, x-litespeed-cache.The thing is that they receive the preview mail and aren’t able to check the preview in such a short time period. Add weekend and different time zones to that, and it makes this plugin pretty much useless because you keep sending preview links back and forth over and over again.
The short timeframe makes the plugin so much worse than it could be. I really don’t understand this choice.
Yes, there is code that you can manually add. But the whole point of a plugin is to stay away from manual coding.
And yes, there is also another plugin that lets you extend the preview time. But that means another plugin to keep up-to-date, more drag on the server and increasing security risks.
So please. You can make this plugin 90% better just by increasing the timeframe, or letting the user decide the timeframe.
]]>To begin with, I would like to thank you for developing and providing this plugin to the WordPress community.
I have been a user of the plugin for the last few years and I am sorry to discover that after the recent updates, the Facebook connected profile constantly expires. This strange behavior leads to unforwarded social messages to Facebook and persists even after successfully having “refreshed” the profile connections. In fact, this also happens even after completely deleting the profile and linking it back again.
I shall be most grateful if you could provide any assistance on the issue.
Thank you in advance.
Best Regards,
George
The cached event page on the server (or on the browser) needs to expire when the event starts or ends. To do that I have added expires and cache-control headers to the page.
Question 1:
Just to make sure I’m on the right path, is this the correct approach to avoid showing stale content to the end user or should I be doing something different?
Sending expires and cache-control headers appears to work mostly but fails under certain circumstances, and that’s where I really need help.
To add the headers I have hooked into the send_headers action and added Expires and Cache-Control like this:
header( “Cache-Control: max-age=$max_age, must-revalidate, proxy-revalidate, public, no-cache”, TRUE );
header( “Expires: $expires”, TRUE );
To make that work with W3TC I must turn OFF the Browser Cache settings for “Set expires header” and “Set cache control header”. If those settings are turned ON then my headers are simply overwritten by W3TC.
I would like to turn those settings ON in W3TC so that default expires and cache-control headers are sent for other pages but I would like to be able to replace those headers for my event pages.
Question 2:
Is there any way for my code to replace the default expires and cache control headers sent by W3TC when those settings are ON?
I have tried using different priorities (1 and 1000000) for the send_headers action hook but the result is always the same. Is there another hook I should be using or do I need to do this in some other way?
Again, sending the expires and cache-control headers with the page works mostly when those settings are off. But a second problem occurs if I refresh the page in the browser. When the page is refreshed the result sent from the server never includes the original expires or cache control headers that I added. The server may return a 304 when “Set Last-Modifier header” is turned ON, or it may return a 200 when that setting is OFF but in either case the response headers never contain the expires or cache-control headers that I originally added. The behaviour on the browser is that the page does not expire and the stale content is shown.
Strangely, when I turn on debug for W3TC at the bottom of the page I see the debug content like “<|– Performance optimized by W3 …” and it includes the original cache-control header “Cache-Control: max-age=900, must-revalidate, proxy-revalidate, public, no-cache”. However, when I inspect the headers (Firefox Web Developer > Network) the cache-control and expires headers are not there. I assume that is because I am receiving a cached copy of the page which contained the information about the headers sent when the page was originally created but those same headers are not sent with the cached response. Note that this makes the debug information unreliable.
Question 3:
Is there some setting or anything else I can do to cause W3TC to re-send the original headers including expires and cache-control with the response sent from the cache whether it’s 304 or 200?
I have been trying to work through these problems for days now and I’m not sure what else I can try. I really need some advice and guidance, and I appreciate your help with this.
Thank you,
-Dave.
Is there a way to make this button say “Place Order” no matter what is in the cart?
Also, I would like to change the text from EXPIRY to EXPIRES if possible.
Thank you and I hope you are having a wonderful weekend!
]]>I’m still struggling with this topic.
I can’t make “send listing for approval” appear when a FREE SUBMISSION listing expires.
When a free listing expires, it just lets me delete it.
Hopefully there’s a solution.
]]>I’m trying the Pay Per Listing option. I activated the option “Automatically approve Reactivating property request?” in “Properties” thinking it would give the option to reactivate the listing once it expires after the days set in “Payment & Submission Type”.
I would like to know if there is a way for the user or agent to reactivate a listing once it has expired.
Thanks before hand.
]]>