PURGUE FOR EDITOR

The editor role can update many plugins, and will be amazing if they can purgue to to makes their changes live. Otherwise the Editor role lost his functionality.

[stefanfisk]

A customer just asked me about this after they cleaned up the roles of their employees.

I can see that there is a Nginx Helper | Purge cache capability added on action, but AFAICT it is not actually used? The purge buttons seem to just check current_user_can( 'manage_options' ).

[misthero]

+1

[pratik-londhe4]

@stefanfisk , @misthero

Thanks for the input. We understand where you're coming from, but at this stage, we’re not inclined to add manual cache purge access for the Editor role.

By default, Editors don’t have access to manage site-level tools like plugins or caching — those are admin-level capabilities. Their content changes (publishing, updating, deleting posts/pages) already trigger automatic cache purges, so manual purge control doesn’t feel necessary or aligned with their role’s intended scope.

That said, if there are specific workflows or custom setups where this would make a real impact, we’re open to hearing more and revisiting the decision.

[misthero]

That said, if there are specific workflows or custom setups where this would make a real impact, we’re open to hearing more and revisiting the decision.

Thank you for your explanation—I agree that, by default, non-admins shouldn’t be able to tinker with caching. However, the issue comes up when you assign the manage_options capability. Granting that to an editor (or to a custom role sitting between Editor and Admin) effectively hands them almost all the same privileges as an administrator, simply so they can flush the cache.

Many sites need a more granular approach—one that lets you grant exactly the permission to clear cache without opening access to every setting under Settings. At the moment, developers are forced either to make cache-flushing users full Administrators or give them the overly broad manage_options capability.

I’d respectfully suggest introducing a more specific capability (or a new, custom one) dedicated solely to cache management (purge), so roles can be empowered to clear caches without inadvertently gaining full admin access.

In our use case, if that's not too much to ask, we would prefer two separate capabilities for purge all and purge url.

I whink this way you would achieve the goal to not add manual purge cache to Editors. But leave the option to devs or admin to control exaclty who can work with cache purging, if needed, without opening them to edit the plugin configuration of this or other plugins.

[stefanfisk]

This was resolved in #420.

[im3dabasia]

Thank you all for your contributions to this feature request. With this PR (#442), the plugin now allows site admins to choose the roles that should be granted purge access.

This feature will be included in the next plugin release. Feel free to try it out and let us know if you need any help