Has s2Member v150722 changed caching with the Expires header?
-
Since updating to v150722, on any pages where I have an s2If shortcode (which is most of the site), I get an HTTP Expires header like:
Expires: Wed, 11 Jan 1984 05:00:00 GMTThis breaks server-side page caching with W3TC, which was working before this update. Only pages for users who aren’t logged in are cached.
If I disable s2Member, pages are still cached, but I can’t do that on the live site because the shortcodes will stop working, of course.
- The topic ‘Has s2Member v150722 changed caching with the Expires header?’ is closed to new replies.
