Open paltman opened 13 years ago
Maby adding a TIMEZONES_USERTIME_CALLBACK
setting that would be a dotted path to a callable that is passed a datetime and a user object. Then a usertime
filter could easily call that and an account app could implement the specific ORM call.
turn this:
{{ match.start|localtime:request.user.account_set.all.0.timezone|date:"n/d/y"}}
into this:
{{ match.start|localtime:request|date:"n/d/y"}}
In addition, pull the timezone out of session if it is there than hitting the database every single usage of the template filter.
I realize that this is a boundry crossing into Accounts so might be more appropriate elsewhere.