WordPress.org

Ready to get started?Download WordPress

Forums

W3 Total Cache
Transients never seem to expire (9 posts)

  1. VicePrez
    Member
    Posted 3 years ago #

    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?

  2. VicePrez
    Member
    Posted 2 years ago #

    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.

  3. Frederick Townes
    Member
    Plugin Author

    Posted 2 years ago #

    Can you please provide code/steps to duplicate?

  4. VicePrez
    Member
    Posted 2 years ago #

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

  5. Frederick Townes
    Member
    Plugin Author

    Posted 2 years ago #

    Of course!

  6. VicePrez
    Member
    Posted 2 years ago #

    Alright. Just sent you the email.

  7. Frederick Townes
    Member
    Plugin Author

    Posted 2 years ago #

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

  8. VicePrez
    Member
    Posted 2 years ago #

    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.

  9. Frederick Townes
    Member
    Plugin Author

    Posted 2 years ago #

    This issue should be gone in the latest releases.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic