From f0edc94f59ba82bef04d0576174035fd0f67a649 Mon Sep 17 00:00:00 2001 From: Alexander Sulfrian Date: Fri, 1 Aug 2014 16:43:00 +0200 Subject: Reporting: do not duplicate isstale functionality The interaction entries have a isstale() method, we do not need a template tag, that tries to figure out this on its own. The isstale() method works even better: It knows, if the interaction is the current interaction and compares the timestamp to the current time or (if it is not the current one) it compares the timestamp to the timestamp of the next interaction. So using the method of the model, you can browse the interaction history and see, if the host was stale some time in the past. Previously all interactions more than 24h ago were marked stale. --- src/lib/Bcfg2/Reporting/templates/clients/detailed-list.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/lib/Bcfg2/Reporting/templates/clients/detailed-list.html') diff --git a/src/lib/Bcfg2/Reporting/templates/clients/detailed-list.html b/src/lib/Bcfg2/Reporting/templates/clients/detailed-list.html index 33c78a5f0..6a314bd88 100644 --- a/src/lib/Bcfg2/Reporting/templates/clients/detailed-list.html +++ b/src/lib/Bcfg2/Reporting/templates/clients/detailed-list.html @@ -32,7 +32,7 @@ This is needed for Django versions less than 1.5 {{ entry.bad_count }} {{ entry.modified_count }} {{ entry.extra_count }} - {{ entry.timestamp|date:"Y-m-d\&\n\b\s\p\;H:i"|safe }} + {{ entry.timestamp|date:"Y-m-d\&\n\b\s\p\;H:i"|safe }} {% if entry.server %} {{ entry.server }} -- cgit v1.2.3-1-g7c22