Purge Cache

  • Resolved mukaaartz

    (@mukaaartz)


    1 year, 11 months ago

    Hello,

    Thank you for creating this wonderful plugin. Super happy with the way it works!

    Though I have one issue, I use the config file method to cache the posts and I have set the time to 4 hours. The problem is, the plugin only updates its list after every 4 hours so if I delete any post or change the status, I get 404. I’m using this plugin for next previous post links and every now and then I get a random 404 page while navigating between posts.

    It would have been better if plugin automatically purged the cache every time the status of posts in plugin’s cache changed instead of throwing empty or draft URL.

    Is there anyway I can purge the cache manually through dashboard area with maybe a PHP code instead of opening config file every time?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Christoph

    (@camthor)

    Thanks!

    Unfortunately, there is no dashboard. ??

    Yes, I see the problem. It should be possible to hook into the event whenever a post is created/deleted/changed and then delete the cache. I will put it on my to-do list.

    Thread Starter mukaaartz

    (@mukaaartz)

    Oh, thank you so much for considering it ??

    Also, I have quite a few posts and if I use rewind once, I get an error that post ids cannot fit which I understand why. Am I supposed to ignore it or it affects the plugin’s performance?

    Feature request: It would have been cool if there were at least some options in the backend to disable rutpdebug, cookie, cache or other dev only parameters or maybe they only worked if you are logged in because right now, I feel like there are just too many openings as anyone can make the plugin do something on the frontend by changing the parameters even if they are not logged in :/

    Thank you in advance if you consider it too in the future!

    Plugin Author Christoph

    (@camthor)

    The number of posts might not be a problem for visitors who don’t actually exhaust the max length of the cookie. I don’t know what happens otherwise – maybe they would see a post twice. I have not yet found another way without using sessions or accessing browser storage.

    So far I just saw the risk of a malicious user disabling the caching. I still hesitate to go the step towards a backend for settings etc. Currently the plugin is simple but powerful, although advanced users need to use constants. I certainly could add another constant that disables debugging if that would be an improvement. Regarding other parameters, it is not much different than any URL where any visitor can change /?p=… or /?s=… .

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Purge Cache’ is closed to new replies.