A simple module to clear all the site caches. This module has its own permission setting so that certain users, based on role, may clear the cache without needing access to the full Site Configuration or Site Performance settings. This is useful for "semi-admin" users such as content editors.

Sandbox project URL: http://drupal.org/sandbox/quinns/1097888

Comments

quinns’s picture

Status: Active » Needs review
quinns’s picture

Any idea when I might be able to have this reviewed? This is my first module submission so I do apologize if I did not follow the steps correctly.

mermentau’s picture

Any idea when I might be able to have this reviewed?

From what I see it's going to be a while. I have one in the process too so have been watching the process. Looks like the list is growing way faster than the review process is.

RobLoach’s picture

The Admin Menu and Devel provide much of the same functionality. You might want to get in touch with the issue queue for those modules and see if you can add any functionality that your module has and is missing in those modules and add it in there?

Other then that, nicely done :-) .

greggles’s picture

Status: Needs review » Needs work

You have:
package = Caching

In your info file. Packages only make sense if a site is likely to have at least 4 items in the package. I don't think caching is a popular enough idea to have that as a package.

      drupal_set_message(t('All caches have been flushed at ').date("Y-m-d h:i:s a"));

That would be better as:

      drupal_set_message(t('All caches have been flushed at @date', array('@date' => date("Y-m-d h:i:s a")));

There's one other potential issue I'm discussing and will report back on shortly. If I don't get back to this in a week please contact me.

tim.plunkett’s picture

Component: new project application » module
Status: Needs work » Closed (won't fix)

Closing, feel free to re-open if this was a mistake.

greggles’s picture

The other issue was about clearing the cache without any csrf protection. It seems that this is not a well decided situation but at least it should be documented that it doesn't have csrf protection and is open to abuse (i.e. that the module is best installed only on dev sites).