Opened 16 years ago
Closed 16 years ago
#7685 closed defect (worksforme)
Timeline default_daysback change not effective
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | timeline | Version: | 0.11.1 |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I have a pretty vanilla trac install that was upgraded from 10.4 to 11.1 by source tarball. I tried to cut the timeline view back from 7 to 3, but even after restarting apache, the change doesn't seem to take effect.
I asked on the irc chat and checked both mailing lists but didn't see anything relevant.
This install is:
- running on rhel 5.2
- python 2.4
- postgresql db
Does this change require an tracadmin env upgrade?
Attachments (0)
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
This may be a non-issue. The default_daysback appears to not override what the user has selected.
If I change my daysback to 3, it sticks, even for new browser logins. Sorry, didn't realize this was stored per user.
If this is working correctly and I just misunderstood, pls just close it.
comment:3 by , 16 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Yeah, timeline filters are remembered in each users' session attributes. default_daysback should work fine for anonymous users or new users who haven't already set something different for that value.
relevant part of trac.ini