Opened 16 years ago
Closed 16 years ago
#7964 closed defect (worksforme)
New milestone doesn't show up in drop-down lists
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.11.2 |
| Severity: | normal | Keywords: | needinfo verify |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
This is on Linux with Python 2.5.2, Apache 2.2.0, mod_python 3.3.1, Trac 0.11.2.
When I create a new milestone from the Roadmap view or from the Admin module, I can see the new milestone listed in the Roadmap view but I don't see it listed in the Milestone drop-down list on the New ticket or Change Properties forms.
When I rename or delete an existing milestone, I get an internal error saying the milestone does not exist as soon as I try to view a ticket.
If I restart apache, everything works fine (until I create/delete/rename another milestone).
This does NOT happen on Windows with tracd (running a copy of the same Trac environment).
Attachments (0)
Change History (7)
comment:1 by , 16 years ago
comment:3 by , 16 years ago
To be more specific, it's sqlite 3.3.17 on the Linux machine where I'm having the problem and it's sqlite 3.4.2 on the Windows machine where everything works fine.
comment:4 by , 16 years ago
| Component: | general → ticket system |
|---|---|
| Keywords: | needinfo verify added |
| Milestone: | → 0.11.5 |
Hopefully it's not a bug related to #6436 …
Maybe it only happened during a "live upgrade" of Trac from 0.11.1 to 0.11.3, i.e. an upgrade done without restarting the server (which is something not advised to do), and then some of the processes where running 0.11.1 and others 0.11.2?
Does that still happen? And with 0.11.3 or newer?
follow-up: 6 comment:5 by , 16 years ago
My guess is that your trac.ini is probably not writable by the apache user. Then the ticket field cache cannot be invalidated by touch()ing the config file.
On Windows, chances are that your trac.ini is writable, if you launch tracd as your own user.
comment:6 by , 16 years ago
Replying to rblank:
My guess is that your
trac.iniis probably not writable by the apache user. Then the ticket field cache cannot be invalidated bytouch()ing the config file.
Yes, that was it. The file is owned by user trac / group trac, user apache is also part of group trac, but the mode of the file was 644 so it was not writable by apache.
chmod 664 trac.ini fixed everything.
Thank you very much.
comment:7 by , 16 years ago
| Milestone: | 0.11.5 |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
Great, closing then. I'll add a note to TracIni about this.
What database backend are you using?