Feature Request: Option to choose which WordPress roles have permission to clear cache

[danielmt2k]

Hi,

In a multisite environment, not all the users publishing content should be an administrator.

So, it would be great to add the possibility for the non-admin users (i.e., an editor) to have the button to clean the cache for their website.

Regards.

[raamdev]

@danielmt2k Thank you for the feature request. I'm sorry you didn't get a response on this. I think it would be a great idea to have an option to choose which WordPress roles have permission to clear the cache. I'll add this to my todo list.

[raamdev]

Removing "Multisite" from the title of this Feature Request, as this feature would be relevant to both multisite and non-multisite installs.

[raamdev]

Also requested here: http://wordpress.org/support/topic/how-can-editors-clear-cache

[Caroline-Elisa]

Yes please!

[raamdev]

Adding this to the Next Release milestone to work on in the current development cycle.

[danielmt2k]

Great!!! It will be very helpful.

Thanks.

2014-09-05 2:27 GMT+02:00 Raam Dev [email protected]:

Adding this to the Next Release milestone to work on in the current
development cycle.

—
Reply to this email directly or view it on GitHub
#68 (comment)
.

[raamdev]

Custom WordPress Capability

It may also be worth adding a custom WordPress capability (see http://codex.wordpress.org/Roles_and_Capabilities) that site owners could use to create custom Roles for their users to give specific roles the ability to clear the cache.

[danielmt2k]

Thanks for including this suggestion too. It would be really great.

[jemoreto]

+1 for clear the cache by editors!
Cheers

[phwconz]

+1 also for allowing Clear Cache for Editors.
Is there any update on when this will be implemented?

[raamdev]

@phwconz This feature request has been made a priority feature for an upcoming development cycle, so it shouldn't be long before you see this in ZenCache. :-)

[andreaarden]

Yeay! Will the ZenCache feature work for custom roles too? I use a WP
plugin to create a custom role for clients, usually not based on the editor
role.

On Wed, May 27, 2015 at 10:57 AM, Raam Dev [email protected] wrote:

@phwconz https://github.com/phwconz This feature request has been made
a priority feature for an upcoming development cycle, so it shouldn't be
long before you see this in ZenCache. :-)

—
Reply to this email directly or view it on GitHub
#68 (comment).

[raamdev]

Will the ZenCache feature work for custom roles too?

@andreaarden Yes, we'll make that possible. :-)

It looks like we should be able to use the WordPress get_editable_roles() function to retrieve a list of roles that is then presented to the site owner as a series of checkboxes, allowing the site owner to select which roles should be able to see and use the "Clear Cache" button in the toolbar.

[danielmt2k]

Hi,

Has this feature been added to ZenCache?

Regards.

[jemoreto]

Waiting for this feature too!!
Thanks

[raamdev]

Next Pro Release Changelog:

• New Feature: It's now possible to specify which WordPress Roles/Capabilities are allowed to clear the cache from the WordPress Admin bar. A new option inside Dashboard → ZenCache → Plugin Options → Manual Cache Clearing allows specifying a comma-delimited list of Roles and/or Capabilities under, "Also allow others to clear the cache from their Admin Bar?". If a user has an allowed Role/Capability, they will see the "Clear Cache" button in their Admin Bar. This feature is also compatible with WordPress Multisite Networks, allowing a Network Administrator to define which Child Site roles should allow a Child Site user to see the "Clear Cache" button for their Child Site. Props @danielmt2k @jaswsinc. See Issue #68.

[danielmt2k]

Thanks Raam for listening to suggestions!!! Great!!!

[raamdev]

ZenCache Pro v151002 has been released and includes changes from this GitHub Issue.

See the v151002 release announcement for further details.

---

This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#68).