Expiration Grid
| Project: | Boost |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Create a grid for ways that a node can be expired, and what actions expire what pages.
These "Actions" can currently flush a node (they call boost_expire_node):
* Voting API
* Comments
* Nodes
Once That node has been signaled to be flushed, it can flush:
* Self
* Front page if promoted
* Tagged taxonomy term pages
* Other items contained in the menu it belongs to (nodes, views, ect...)
* CCK node reference fields
* Views containing this node
There is also the option of killing the file or merely marking it as expired in the database.
Example:
New Comments - Kills: Node, and views. Not: front page (if promoted), CCK references, taxonomy terms
Edited Node - Kills: Node, front page, CCK references, views. Expires: taxonomy terms
New Vote - Expires: Node. Kills: Views. Not: Front page, CCK references, taxonomy terms
Open to ideas, patches, ect... this will take some time to do.
