Cache Conflict

  • Resolved rajaito

    (@rajaito)


    5 months, 1 week ago

    Hello, I am using this plugin to auto expire a custom post type on a website hosted with Kinsta. We found that with Kinsta’s cache enabled, the posts were not expiring properly (they still showed after the expire date). So we added a cache exclusion for the custom post type. Now the site is getting severe performance drops because these pages get a lot of hits. Ideally, we would not exclude the posts from the cache but instead have the cache for the specific URL automatically cleared when PublishPress Future runs. Do you have a recommendation?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Hi @rajaito

    Thanks for using PublishPress Future.

    Our expiration is triggered by WP Cron, which requires a site request to be passed through to normal PHP script execution.

    If a page is being cached, there’s no way that a site user hitting that cached page is going to trigger our PHP script to update it; there has to be some non-cached site request to trigger the WP Cron.

    What I could suggest you in this case is setup real cron instead of WP Cron. You could get in touch with Kinsta on this one so they can guide you on how to setup real cron.

    Thread Starter rajaito

    (@rajaito)

    Thank you for this info.

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @rajaito You are most welcome ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.