Thread: CC Beta 3.6.7* is now production as V3.6.8
View Single Post
Old 05-18-2015, 08:35 AM   #23
NSILMike
Guru
NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.
 
Posts: 735
Karma: 35936
Join Date: Apr 2011
Location: Shrewsury, MA
Device: Lenovo Android Tablet
Quote:
Originally Posted by chaley View Post
The way auto-delete is currently implemented the value in CC is the minimum number of days that must pass before a book will be deleted. I did this because I thought it was safer, but thinking about it more I realize that my scheme is potentially dangerous.

The problem: the user must set this number to the lowest value desired and existing in the cc_delete_after_ tag. This means that news without a tag will be deleted using that low value. It would probably be safer if this number be the default and permit the cc_delete_after_ tag to specify a lower number. That way the user can specify a higher number which will apply to new feeds and feeds without the tag.

Comments?
How and/or where do I modify the cc_delete_after_ tag? Is it in the recipe, or...?
NSILMike is offline   Reply With Quote