Skip to content

2 Comments

  1. Uriahs
    October 21, 2017 @ 8:33 am

    Why don’t you contact the authors and let them know? I’m a little confused as to what you are pointing out in the article. I do use Yith Wishlist and the built-in recently viewed products widget.

    Which caching plugins cause this? What did you use in your tests?

    I can simply disable caching on the wishlist page, but the recently viewed has to be dynamic, are you saying caching plugins usually cause it not to be?

    Reply

    • Anon
      October 23, 2017 @ 9:55 am

      What I was trying to point out is that there are some plugins which create content on your site unique to each USER or VISITOR. For example – a wishlist basket, that’s unique per user. Recently viewed products – unique per user. You can probably think of others.

      These plugins, depending on how they are coded, prevent the use of page-caching because if you cache a page for User A you cannot present it to User B.

      Well written plugins would have the exact same code on the page for User A and User B but would retain a cookie on User A’s computer or User B’s computer and then JavaScript would be used to contact the server and fetch the unique contents for this user.

      I did try contacting Yith through their support pages – they may have fixed it by now, I have not checked recently, but back when I checked, the advice from Yith was to ‘disable your page caching’ – hardly a viable approach for a scalable website.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *