• Resolved izreview

    (@izreview)


    After the latest update, my transients started to behaving irregular. My plugin can use transients but i cant see them under wp_options. I know, they exist but I see them expired. It might be memcache related? When I disable litespeed, everything backs normal. Do you have ani idea?

    Last Report Number: SXJCGTDB

    Last Report Date: 03/05/2026 13:35:35

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Support litetim

    (@litetim)

    @izreview in the latest version all transients are saved to Object cache(either Memcache or Redis) when OC is enabled.

    Thread Starter izreview

    (@izreview)

    When “Object Cache” disabled, backed to normal. Is this influence overall performance in bad way? I believe it will. Is there any way not to save transients to OC, but enable OC as before? which will be much better I think.

    Plugin Support Hai Zheng⚡

    (@hailite)

    Could be same reason by https://wordpress.org/support/topic/site-health-on-dashboard/#post-18842224

    Can you try to set that TTL to weeks or a month to see?

    Thread Starter izreview

    (@izreview)

    Changed “Default Object Lifetime” to 604.800 seconds, but not changed. All transients seems to be expired as soon as created.

    Thread Starter izreview

    (@izreview)

    My site is in a shared hosting environment. In Litespeed Cache\Object “Object Cache” option is ON. But, Status is like that :

    Status

    Memcached Extension : Disabled
    Redis Extension : Disabled
    Connection Test: Failed Learn More

    Is that means, I’m actually not using Object cache already and not getting performance benefits already? If the answer is yes, switching OFF the “Object Cache” seems a reasonable solution for me. Is there any benefit of this Object Cache ON, in this situation?

    Sincerely.

    Plugin Support litetim

    (@litetim)

    @izreview yes, you are right. If that is the status overview, then no Object cache Extensions enabled.
    Please disable Object cache and test the site.
    In some situations(Object Cache) speeds up the site by using a faster solution to store data.

    Thread Starter izreview

    (@izreview)

    I have downgrade to 7.7, seems fine now.

    Plugin Support litetim

    (@litetim)

    @izreview ok, that is something that temporary fixes the issue.
    Please help us debug the situation:
    your ObjectCache is active
    Is Redis or Memcache library active and have the correct setup?
    The connection can be established, yes?

    Plugin Support Hai Zheng⚡

    (@hailite)

    If you have OC running and extension running correctly, please also try do this in v7.8:

    Change $ttl = $expire ? $expire : $this->_cfg_life; to $ttl = $expire; in https://github.com/litespeedtech/lscache_wp/blob/c388f41128b43b812787df21ca53b7b6c06d5d4a/src/object-cache.cls.php#L678 to see if that resolve the issue or not. TIA.

    Thread Starter izreview

    (@izreview)

    Yesterday I asked my hosting provider to enable Memcached, and since then I get some improvement. Now, transients are not being expired as soon as created. Instead I can see transients from my plugin, but still can’t calculate/determine transient life. I believe, I can manage to handle this with minor re-programming’s.

    In short, my problem’s source seems like not having memcached, but enabling Object Cache. In that configuration, it was working without problem, but after 7.8 version update, I get issues related to transients.

    Ps* I tested your config change ($ttl = $expire;), but not seems working. (backing original config)

    Plugin Support litetim

    (@litetim)

    @izreview we are looking into.
    We have this build: https://github.com/timotei-litespeed/lscache_wp/commit/cd84682e75f62a94a1a415c7d21c2e8112873e14
    Thank you for understanding

    Plugin Support Hai Zheng⚡

    (@hailite)

    The transient issue has been improved on master branch v7.8.0.1-rc1. Please give it a try via Beta Test from Toolbox.

    Plugin Support litetim

    (@litetim)

    @izreview the fix we added is present in 7.8.0.1. Please confirm the fix works for you

Viewing 13 replies - 1 through 13 (of 13 total)

You must be logged in to reply to this topic.