0

A customer of ours has reported a "bug" that their live site works differently from the staging environment. What they see is that when a user selects "all" products on a category page, then changes categories, the selection reverts to the default number of items per page items on live but stays at "all" products on staging.

What we found was that the live site had Full Page Cache (FPC) enabled and the staging site had it disabled. Once FPC was enabled on staging server, we were able to replicate the issue in that environment. Checking further, this happens on all of our EE sites and I guess I had never tested/noticed it before.

I understand that FPC is storing a version of the page as generated with the default parameters, but, is there any way to generate the non-cached behavior without using a new URL that includes the show parameter?

Thanks

Improve this question
1
  • You will have to hole punch it, we don't have the exact settings at hand so someone else will be able to assist. We generally don't use FPC for various reasons, and average ~1s dynamic page loads (~500ms product page loads) so avoid all these problems. The problem with caching is always the same, invalidating it. You might want to reconsider the approach, EE installs we have come across switch off the internal FPC and use something more reliable.
    – user2935
    Jul 10, 2014 at 14:56

1 Answer 1

Reset to default
1

Category filtering is initially applied by URL argument, but when this is done the filter selections are also stored in the users session. When the user navigates to another category after applying filtering, the filter selection stored in the session is used to filter the category and you don't see any URL arguments. The EE FPC is not taking this session data into account when loading category cached content and is purely caching by URL.

If you want this to work using the standard EE FPC then you will need to have it customised to consider this session stored filter data.

Alternatively you may want to consider Evolved Caching which is a much more complete caching solution which, amongst many other benefits, does consider this session stored filter data (and yes it does work under EE).

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.