As was pointed out to me on s2member's forum, "Don't be a dolt!" Well, Philly there was more polite ...
“If you cache pages for logged in users (which are likely to be members) then you are going to serve them to non-members that are not logged in”
Good point.
“I’m not aware of any option which allows a cache to be created for logged in and a separate cache for logged out members.”
** Now that would be nice! **
I saw this in s2's cannily titled no-cache-inc.php, applying to logged in users:-
if (!defined ("DONOTCACHEPAGE"))
define ("DONOTCACHEPAGE", true);
But, as Philly suggested, maybe this is best left alone.
But, but, well, how ruddy frustrating. I’d like to be able to offer a fast site to paying members, as well as to guests. Seems only right! Might there be some kind of workaround?
… Some use of fragment caching, f’rinstance? I see that w3TC supports that now.
Any keywords gratefully received, happy to research and post back anything useful.
