[allura:tickets] #7852 Don't update mod time when viewing artifact creates a cache

[Dave Brondsema <da...@brondsema.net>]

- **labels**:  --> sf-current, sf-2



---

** [tickets:#7852] Don't update mod time when viewing artifact creates a cache**

**Status:** open
**Milestone:** unreleased
**Labels:** sf-current sf-2 
**Created:** Thu Mar 12, 2015 02:56 PM UTC by Dave Brondsema
**Last Updated:** Sat Mar 14, 2015 01:07 AM UTC
**Owner:** nobody

In addition to the fixes done in [#7834], a ticket can still be marked as updated just when viewed.  This happens if the cache was not created initially (e.g. ticket import - no view, or first view was under the threshold time) and then the cache was created upon a later view.   We need to skip updating `mod_date` and `last_updated` when a cache is set.  I think it's probably safe to set the `skip_mod_date` and `skip_last_updated` flags on the session, since there shouldn't be cases of rendering a markdown (viewing) in the same session as legitimately updating records (I hope).


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.