• Resolved salmanmir

    (@salmanmir)


    Hi
    I have a problem with crawler. my website pages are mostly same for guest and logged in users, so I wanted to cache my logged in users pages as a public pages, to cache them for all of the users. so I set “cache for logged in user” button to off, and wrote my pages addresses regex in “force public cache” section. (to cache those pages for logged in user as a public pages.)
    Now, when I crawl the sitemap with user simulation ID, it always shows that all the pages are already cached! (I have a crawler for guest users before this crawler). But when I open the website in browser as a logged in user, it doesn’t hit at first time. (refreshing the page or viewing the page with other logged in user after that would be hit.) So I absolutely sure that the problem is in the crawler section.
    Can u help me with this problem?
    Report number: SERNJHDP
    Report date: 07/23/2024 10:05:39
    Regards,

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support qtwrk

    (@qtwrk)

    yes, it doesn’t work that way , you will need to enable ESI , but ESI may not be compatible with certain plugin or theme , so you need to test it out.

    Thread Starter salmanmir

    (@salmanmir)

    so what do you mean by writing “To cache pages for users with the “Subscriber” role, choose one user that has the “Subscriber” role, and enter that user’s ID in the box.” in page with link below: https://docs.litespeedtech.com/lscache/lscwp/crawler/#simulation-settings-tab

    Plugin Support qtwrk

    (@qtwrk)

    like get the one user’s ID of subscriber roles and put into role simulation field

    Thread Starter salmanmir

    (@salmanmir)

    No. I mean this example is not right. the page will not be cached for other subscribers.
    I want to do the same for my customer.

    Plugin Support qtwrk

    (@qtwrk)

    that’s the part you need ESI

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.