Configuring Page Cache for a Subscription site

  • ABOUT THE SITE:
    – Subscription based news/business/investment advice – we have around 10,000 paying subs and at any one time have approx 1,000 trials
    – Our business revolves around a free trial then to onboard trials into paying subscribers
    – Login to access our content behind the paywall
    – We host with Rackspace with a 4 web server cluster
    – We have Object, Browser, Fragment Cache, CDN with Rackspace

    What work we need done includes:

    – We want Page Cache to work. When we turn it on, the site loads correctly (before it didn’t) however it would mess around with the login function for subscribers. It breaks in two ways:

    1. when you log in with username and password – it does not tell you whether you have been successfully logged in or not (so user will have no idea what their status is); but more importantly;
    2. it would show the last authenticated user who had logged into the system. This means should anyone wish to click “Manage Profile” that that user’s personal details (including payment information) – albeit, it only shows last 4 digits of their credit cards but nonetheless will be displayed for the world to see be they logged in or not.

    What I think we need is to write exceptions to the Page cache for all functions associated with login function and Manage Profile. I believe this will then prevent these details from being displayed to all users and to ensure the login function works uniquely for each user.

    https://www.ads-software.com/plugins/w3-total-cache/

  • The topic ‘Configuring Page Cache for a Subscription site’ is closed to new replies.