• Resolved peterdredd

    (@peterdredd)


    Hello,

    I recently installed litespeed cache.. and it’s looking good, but the object cache settings page won’t save .. every other settings will save but this.

    Tried changing to redis with the appropriate settings but it reloads to show the same default settings, while options saved is showing.

    How do I fix this?

    Thanks

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

    (@qtwrk)

    you mean it reload back to Memcached/11211 or something ?

    and please check the http response header on this page when it reloads.

    Thread Starter peterdredd

    (@peterdredd)

    @qtwrk
    Thanks for your response.

    I was able to fixed that by increasing php values, created a new .htaccess file, deactivated the plugin, cleared its data in database.. Then I reactivated it and the settings saved this time.

    However, I noticed another error.. what’s shown to me as a logged in user is quite different from what visitors see.

    To me, I can see the sticky menu website logo while scrolling.. also Twitter urls automatically changes to the posts/tweet in website.

    But for visitors, the menu and logo is not sticky.. Twitter urls won’t display the media. Only shows the written texts.?

    How do I set it to show as it is to me, a logged in user, to visitors too. Or enable this options for visitors.

    I disabled disabled all features to check if it’s from the plugin.. checked the post in incognito and its now showing the video instead of the text and url. So it s the plugin.

    How do I get the Twitter urls changing to video and the sticky logo and menu bar working while the plugin is active?

    Plugin Support qtwrk

    (@qtwrk)

    please do me a side-by-side comparison screenshot on login and not-login users

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Object cache won’t save after switching to Redis’ is closed to new replies.