Transients never seem to expire

  • I’m retrieving two values of the same transient, the actual transient value itself, along with its timeout value. The transient seems to have no expiry date. I compared the UNIX time differences between the expiry date of the transient and present time. W3 Total Cache seems to have cached the value for over 7 days ahead of its expiry period.

    When I cleared all caches and disabled the plugin, the problem got resolved.

    Is there any way this can be resolved without disabling the plugin? Perhaps I can temporarily disable the object cache temporarily until the next release?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter VicePrez

    (@viceprez)

    Even though i posted this over a month ago. I’d like to point out that disabling object cache solved the problem. I’m still looking for a more practical solution that doesn’t involve disabling object cache. Any suggestions on how to keep it enabled and respect transient expiry dates is appreciated.

    Thanks.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Can you please provide code/steps to duplicate?

    Thread Starter VicePrez

    (@viceprez)

    Hey Frederick. If you don’t mind. Could i email you a pastebin of the code?

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Of course!

    Thread Starter VicePrez

    (@viceprez)

    Alright. Just sent you the email.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Have I replied? I’m not sure that I have it sorry.

    Thread Starter VicePrez

    (@viceprez)

    Yes, sir. Sure did.

    The initial problem I had was resolved. The second problem, which we discussed, which I have no power over, is the purging of cache when posts and comments are created. Transients set by the user, with a timeout of one week are purged instantaneously once a post/comment is submitted, rendering its purpose useless.

    Don’t get me wrong, purging of cache is useful/necessary when it comes to keeping the website dynamic, but it interferes with user-set transients longer than the specified life-time period via the object cache settings, which are less dynamic and costly to run (i.e retrieving information from foreign API’s which impose strict rate-limiting policies)

    In the event that the cache needs to be purged, a distinction could be made so user-set transients are kept intact while other cached items set by W3TC are purged.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    This issue should be gone in the latest releases.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Transients never seem to expire’ is closed to new replies.