Page cache not working

  • Resolved webpart

    (@webpart)


    2 years, 3 months ago

    After updating from version 3.2.3 to version 3.2.9, everything works fine with page caching if nothing else is done.

    However, if you purge the cache (clicking purge cache or disable/enable cache), write cache settings, …, it stops working.

    Reverting back to version 3.2.3, just save the cache definitions for it to work normally in this version.

    It is not possible to keep reverting to 3.2.3 and later updating to 3.2.9 whenever the cache is purged (for example after updating any plugin).

    I already tried uninstalling and reinstalling the plugin but the behavior is the same.

    The page I need help with: [log in to see the link]

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

    (@vupdraft)

    If you open the JS console do you see any errors? (please see here for a guide: https://updraftplus.com/faqs/how-do-i-open-my-browsers-developer-tools/)
    Do your php error logs show any errors?
    What kind of server are you using?

    Thread Starter webpart

    (@webpart)

    No errors on JS Console.

    Error on php error log:
    [29-Nov-2022 12:00:03 UTC] Cron reschedule event error for hook: wpo_purge_old_cache, Error code: invalid_schedule, Error message: O evento agendado n?o existe., Data: {“schedule”:”wpo_purge_old_cache”,”args”:[],”interval”:0}.

    Windows Server.

    Plugin Support vupdraft

    (@vupdraft)

    If you install the free plugin WPCrontrol do you see more than one hook for wpb_purge_old_cache in the Cron Schedules?

    Thread Starter webpart

    (@webpart)

    Yes.

    wpo_purge_old_cache

    This schedule is added by another plugin and cannot be deleted

    0 (now)
    This interval is less than the WP_CRON_LOCK_TIMEOUT constant which is set to 60 seconds. Events that use it may not run on time.

    Every time after the cache has expired

    wpo_use_cache_lifespan

    This schedule is added by another plugin and cannot be deleted

    0 (now)
    This interval is less than the WP_CRON_LOCK_TIMEOUT constant which is set to 60 seconds. Events that use it may not run on time.

    Same as cache lifespan: 0 hours

    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    I am just asking one of my colleagues to check over this as I don’t think you are the only user getting this message.

    Plugin Contributor Venkat Raj

    (@webulous)

    @webpart I was able to reproduce the issue and will be fixed in our future release.

    I understand that you have reported the issue in other threads as well, but mentioning it as Elementor compatibility issue. Apologies for over looking the issue.

    Until the issue is fixed, please change your cache life span to some other value like 3 months or any value that is not 0. That should fix the issue for now

    Thread Starter webpart

    (@webpart)

    Unfortunately it is not so.

    I had already done the test of putting a value other than 0 in the cache life span.
    In this case, the references in Cron Schedules disappear but the page cache still doesn’t work.
    Preloading the cache doesn’t work either.

    Even after activating/deactivating the cache, saving the settings, … it does not cache the pages.

    I’m back to version 3.2.3 where everything works perfectly.

    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Sincere apologies for the inconvenience. Our development team are working on this and we should have a new release for you soon.

    Thread Starter webpart

    (@webpart)

    Hi,

    Any news about this subject?

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Page cache not working’ is closed to new replies.