Purge all cache, for editors?

Hey!

Thank you for the feedback, it’s super helpful!

I definitely see the need in allowing the option moving forward, but I am a little apprehensive since the plugin isn’t gated to specific selectable user roles at this point in time. I think that functionality would be required before I start adding things explicitly meant to drop all caches on the site, especially since it’s something the WP Engine plugin requires administrator usage for. I’m a little nervous about possible abuse, so I’d want to have the ability to restrict access before adding it. I am not opposed to that change, I just don’t know when I’d be able to get it implemented.

That said, the varnish cache can be dropped using the “Purge Path” option for the entire site. When a “/” is entered into the box, it regex matches all paths for the site and clears it. This would be a work around in this case for this unless object cache needs to be purged as well.

Do you have anymore detail on what sort of changes are being made? Are these theme updates, or anything of that nature? If this is part of a pretty typical workflow, it might be something WP Engine could do automatically.

Thanks!

Thank you Ethan,

We sometimes include excerpts from blog posts or other pages, sometimes in the footer or some banner area across the site but these areas doesn′t reflect updates, because of cache.

You mentioned:
“The varnish cache can be dropped using the “Purge Path” option for the entire site…This would be a work around in this case”
I′m not sure I understand how…is this something that an editor-role could perform from a button or is this a setting that could be triggered after any update to the site?

Right now I′m using User Role Manager to add manage_options to the editor -role which allows for the Editor-role to see the “purge all cache” -button. the drawback is that I need to hide a lot of other unnecessary options that comes with this.
…is there any “possible abuse” that we should watch out for with this method?

Thanks!

I see, My apologies, I assumed the editor could see the plugin page, which they can’t.

The possible abuse would be from someone purging the cache too much, which can cause a load on the site. I don’t think I’d be too worried about it from a one off, but making it a global option could be a concern for other users of the plugin. This is my understanding of why the options is locked down to Administrators.

This seems like something the WP Engine plugin should do, that is exacerbated by the increased cache time. Since the WP Engine plugin doesn’t allow it, I kind of feel like I shouldn’t overwrite those wishes. I’ll bring it up the next time we revisit the Varnish configuration.