This module provides a new permission rebuild cache access. Roles with this permission assigned will see a admin toolbar button Rebuild Cache. Clicking it simply fires drupal_flush_all_caches(). That's it.
I'ld like to mind a similar (and rejected) Drupal core feature request: https://www.drupal.org/node/2870483 and I totally agree with @Berdir's statement:
that shouldn't be necessary in the first place. With cache tags, any change that an editor can make should automatically invalidate all relevant caches. Anything else is a bug IMHO.
Nevertheless in real world I found it necessary quite often to have other users than the ones with the administer site configuration permission being able to flush caches. Thinking especially of front-enders.
https://www.drupal.org/project/rebuild_cache_access
git clone --branch 8.x-1.x https://git.drupal.org/project/rebuild_cache_access.git
composer require drupal/rebuild_cache_access:dev-8.x-1.x
Manual reviews of other projects
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | rebuild_cache_access-fix_coding_standards_errors-2944108-3.patch | 2.57 KB | saivaishnavijupudi |
| #2 | rebuild_cache_access_errors.txt | 2.84 KB | saivaishnavijupudi |
Comments
Comment #2
saivaishnavijupudi commentedI found the above coding standard errors.
Comment #3
saivaishnavijupudi commentedthe patch for the coding standard errors, please review it.
Comment #4
norman.lolThanks a lot @saivaishnavijupudi! Patch reviewed and successfully applied and pushed.
Comment #5
norman.lolUpdated description git clone URL to https instead of user@git
Comment #6
norman.lolUpdated description and added some blank lines for readability
Comment #7
saivaishnavijupudi commentedCan you please give me credit for this patch @leymannx
Comment #8
norman.lol@saivaishnavijupudi Absolutely, yes! But how?
Comment #9
norman.lolAdded review section.
Comment #10
norman.lolAdded review.
Comment #11
norman.lolUpdated review link.
Comment #12
norman.lolUpdated review link
Comment #13
norman.lolComment #14
norman.lolAdded review.
Comment #15
norman.lolAdded review.
Comment #16
norman.lolAdded review.
Comment #17
norman.lolAdded review.
Comment #18
saivaishnavijupudi commented@leymannx please go to credit and committing section and check the checkbox beside my name.
Comment #19
norman.lol@saivaishnavijupudi it already is. I guess this happens automatically.
Other thing I found something strange in your code sniffer output. As namespaced classes, interfaces and traits should not begin with a file doc comment. So the following
1 | ERROR | [x] Missing file doc commentare false positives:Comment #20
norman.lolComment #21
norman.lolComment #22
norman.lolTests added.
Comment #23
mattshoafTook a look through the code and loaded it on a minimal install site.
Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
No: Does not follow the guidelines for in-project documentation and/or the README Template: missing section headings, see https://www.drupal.org/node/2181737, not a blocker since this module is straight forward enough.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
Coding style meets Drupal best practices.
Comment #24
avpadernoThank you for your contribution!
I am going to update your account so you can opt into security advisory coverage now.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewer(s) as well.
Comment #25
avpaderno