zherbert
Forum Replies Created
-
Forum: Plugins
In reply to: [W3 Total Cache] WARNING: Do NOT use W3TC with membership sites!Just a quick update: W3 Total edge never did respond to my email. And obviously, they didn’t respond here either. So it doesn’t appear that any fix is forthcoming.
Forum: Plugins
In reply to: [W3 Total Cache] WARNING: Do NOT use W3TC with membership sites!I haven’t tried that yet. I added a bit of code to the login that alters the redirect url by appending a query string variable after the user logs in.
This prevents the browser caching for that specific scenario. But there are other scenarios where it’s still an issue. (eg. using the password reminder and then returning to the original link.)
I was just doing a quick 3 day promotion on my site. So the registration is down now. Unfortunately, as best as I can tell, W3TC prevented about 95% of the attempted orders from going through. :/
Forum: Plugins
In reply to: [W3 Total Cache] Browser Caching & Logged in PagesI’m sorry, I don’t know how else to explain this… The issue is with browser caching. Not server caching.
I’m on the latest version, but that doesn’t matter. It isn’t about CPU load or directories.
Do you actually work for W3 Edge?
At this point, I have to assume that the needed feature doesn’t exist.
I’ll go ahead and make a separate thread to warn other users against using W3TC on membership sites until the feature is added. And I’ll also send a message to W3 Edge directly to make them aware of the issue so that it can be addressed in a future version.
Forum: Plugins
In reply to: [W3 Total Cache] Browser Caching & Logged in PagesThe problem isn’t PAGE caching. Page caching works great. Everyone is happy with page caching.
The problem is BROWSER caching. And how those two features work together.
Browser caching effectively negates the “don’t cache pages for logged in users” feature.
Because by the time the user has logged in, the browser has already cached that page and so the user NEVER GETS the logged in version.
What we need is a way to tell the BROWSER cache to not apply to certain pages. Or really, to be able to give a list of pages to send NOCACHE tags to the browser. Part of a “total cache” solution should be the ability to tell the BROWSER to never cache certain things.
I’m a little baffled that this hasn’t come up before. Because this is an absolutely showstopping issue. What’s the point in improving performance on your site, if the solution is going to prevent your customers from logging in or submitting orders??
Forum: Plugins
In reply to: [W3 Total Cache] Browser Caching & Logged in PagesI’m having this same issue and was just about to post…
The issue isn’t the server caching. The server caching works fine. (And doesn’t cache for logged in users.)
The problem is that the browser has already cached the logged out version of the page. So when the user logs in, the browser just pulls the from the local cache and doesn’t make the request to the server.
It looks like what we need is a way to set nocache options on certain pages. Or a way to exclude specified pages from the browser based cache settings.
Is there a way to do this? This issue is actually preventing my users from logging in and purchasing!
Well the status page showed all green and said the htaccess file had been updated. But I didn’t know how to find the file over ftp to check.
It’s actually even worse than that.. Because once the first person requests the page over http, it caches the mixed content html.
Thereafter, everyone gets the mixed content. Regardless of the protocol they use.
So basically, a page will work until the first time a person requests it over http. Then it breaks for everyone.
We solved it by creating a server-side redirect rule, to make sure that an http protocol request never makes it to WordPress in the first place.
Yes, it happens after the cache is cleared.
1. Clear the cache in Total Cache
2. Disable Total Cache
3. Close all incognito windows
4. Open a new incognito window and load any page over https (It will work.)
5. Close all incognito windows
6. Open a new incognito window and load that same page over http (It will redirect to https and it will work.)
7. Re-enable Total Cache
8. Repeat steps 3-6
9. It will break on Step 6.