Context Cache is module which lets you control caching and expiration through Context. For example, for one content type you can set its cache for two hours while for another you can set it for 30 minutes.
The Drupal cache applies the same expiration time to all pages on a site, but with this module it can be customized by path, content type, taxonomy, and other conditions. There are other related modules, but not like this one, such as http://drupal.org/project/boost_custom_expire_rules
Coder Sniffer will complain about the class name and the scope modifier, but these errors conflict with the standard way of writing Context plugins, so I did not make the changes. You can see these errors here: http://ventral.org/pareview/httpgitdrupalorgsandboxgeraldmelendez1975776git
Project page: http://drupal.org/sandbox/geraldmelendez/1975776
git clone --branch 7.x-1.x http://git.drupal.org/sandbox/geraldmelendez/1975776.git context_cache
Reviews of other projects
http://drupal.org/node/1999064#comment-7434126
http://drupal.org/node/1997696#comment-7425228
http://drupal.org/node/1987190#comment-7413638
Comments
Comment #0.0
geraldmelendez commentedImproved grammar
Comment #1
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #1.0
PA robot commentedFixed branch.
Comment #2
trof commentedHi geraldmelendez.
The module works perfectly.
Just a small correction:
context_reaction_cache.inc
line 47
need add t() function to description
Comment #3
a.milkovskyPlease consider reviewing coding standarts.
Test your module at http://ventral.org/pareview/httpgitdrupalorgsandboxgeraldmelendez1975776git after each update
Comment #4
geraldmelendez commentedHey guys, thanks for reviewing my module. I meant to work on it last night but I was stuck at work.
I made all the suggested changes except for one:
16 | ERROR | Public method name "ContextReactionCache::options_form" is not in
| | lowerCamel format, it must not contain underscores
http://ventral.org/pareview/httpgitdrupalorgsandboxgeraldmelendez1975776git
This is a Context hook, so the name of the function cannot be changed. The Context module uses this hook to pull in the configuration form.
Comment #5
trof commentedHi geraldmelendez.
Probably Coder Sniffer say something like
104 | WARNING | Code after RETURN statement cannot be executedin file context_reaction_cache.inc
But I think in this case the code is written correctly.
Comment #6
geraldmelendez commentedHey trof,
I'm not seeing that error on my local server or on Ventral (http://ventral.org/pareview/httpgitdrupalorgsandboxgeraldmelendez1975776git)
I only get that one error from line 16
Thanks for the quick reply,
- G
Comment #7
zterry95 commentedcontext_reaction_cache.inc
Line 54
add t() for #description
Comment #8
geraldmelendez commentedHey zterry95,
Thanks for reviewing my module, the description is already passed through a t() function on line 38:
Line 54:
Comment #9
soundessential commentedWorks as described and has pretty clean code. Good work!
Comment #10
geraldmelendez commentedThank you for testing.
Comment #10.0
geraldmelendez commentedNote about errors
Comment #10.1
geraldmelendez commentedAdding my reviews
Comment #10.2
geraldmelendez commentedAnother review
Comment #11
soundessential commentedHere's the review tag.
Comment #12
klausimanual review:
ContextReactionCache::options_form(): the #options label should run through t() also.
But otherwise looks good to go to me, so ...
Thanks for your contribution, geraldmelendez!
I updated your account to let you promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and get involved!
Thanks, 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.
Thanks to the dedicated reviewer(s) as well.
Comment #13
geraldmelendez commentedThank's a lot for reviewing my module and for updating my account. I can't wait to contribute more of my modules.
Comment #14.0
(not verified) commentedAdding my third review