• Resolved mrlukas

    (@mrlukas)


    So I have problem with logged in users cathing.
    How can I achieve this correctly?

    1. I set Crawler Simulation Settings to the customer user role.
    2. Default Private Cache TTL set to 3600 1 hour maximum what I can type.
    3. Cache Logged-in Users ON

    So how can I cache the website for logged in users for longer than 1 hour?
    It can be the same cache as a Public.
    I don’t think I can use Force Public Cache URIs as I am using the translation plugin too.

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

    (@qtwrk)

    Hi,

    unfortunately you can’t

    it is hard coded to max 3600 seconds for private cache

    if your translation plugin does some cookie or query string when translate , you can use that as vary point to create cache vary for public cache

    Best regards,

    Thread Starter mrlukas

    (@mrlukas)

    “if your translation plugin does some cookie or query string when translate , you can use that as vary point to create cache vary for public cache”

    Can you explain in more details?

    Or maybe you can just tell me what kind of options there are for logged-in users catching?

    Plugin Support qtwrk

    (@qtwrk)

    please provide the report number , you can get it in toolbox -> report -> click “send to LiteSpeed”

    Thread Starter mrlukas

    (@mrlukas)

    PXQDOCYN

    Plugin Support qtwrk

    (@qtwrk)

    it leads to me /en/ , how can I switch to different language ?

    Thread Starter mrlukas

    (@mrlukas)

    We use only /EN/ as we translated descriptions from a different language and the base language is different, but we are not using it.

    Plugin Support qtwrk

    (@qtwrk)

    but if you have different URI for different language , the cache should work

    Thread Starter mrlukas

    (@mrlukas)

    So what should I write in the Force Public Cache URI tab?

    Plugin Support qtwrk

    (@qtwrk)

    if you have site language set up like

    /en/
    /fr/
    /de/

    …etc , then just put these lines

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Catch for logedin users’ is closed to new replies.