Motivation

Creating an ideal caching strategy that takes into account all the components on the site is time consuming, and can require many iterations to get right. It can also lead to difficulty when introducing new functionality to an existing site. The caching strategy will almost certainly have to be revisited, otherwise the site may be broken. Most basic sites could benefit from basic views and panels caching, but don't have the budget or time to implement a complex caching strategy. We desire a drop-in solution that can allow basic sites to cache page components without spending too much time on fine-tuning.

Solution / Project Description

This module extends the functionality of the Cache Expiration module by triggering cache expiration on components used to render a page when the page is expired through the Cache Expiration module. Lists of components that are used to render a page are stored. When the Cache Expiration module issues a purge on a path, the components used to render the page at that path is also invalidated. The major pieces of this system use the ctools plugin library to provide swappable functionality.

Resources

Comments

PA robot’s picture

PA robot CreditAttribution: PA robot commented
Status: Needs review » Needs work

There are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxchristophersmith26224...

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then 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.

christophersmith262’s picture

christophersmith262 CreditAttribution: christophersmith262 commented
Issue summary: View changes
christophersmith262’s picture

christophersmith262 CreditAttribution: christophersmith262 commented
Status: Needs work » Needs review

Corrected issues from pareview and added link to the issue summary.

mariano.barcia’s picture

mariano.barcia CreditAttribution: mariano.barcia commented

Hi, this module looks promising. This is my review:

Automated Review

PHP CodeSniffer detected the following issues:

  1. Doc comment for var $data does not match actual variable name $handler at position 2 of /component_cache_expiration/includes/queue/ExpireComponentsExpireQueueItem.inc line 25
  2. Doc comment for var $handler does not match actual variable name $job_id at position 1 of /component_cache_expiration/includes/queue/ExpireComponentsExpireQueueItem.inc line 23

(This was detected by PHPCS in Eclipse, PARreview doesn't detect this, I guess it should).

Manual Review

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 / No: Does not follow the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
Yes: Follows the guidelines for in-project documentation and/or the README Template.
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
None found.

This review uses the Project Application Review Template.

mariano.barcia’s picture

mariano.barcia CreditAttribution: mariano.barcia commented
Status: Needs review » Needs work
PA robot’s picture

PA robot CreditAttribution: PA robot commented
Status: Needs work » Closed (won't fix)

Closing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.