Opened 17 years ago
Closed 12 years ago
#3007 closed defect (wontfix)
[0.11] color not rendered
Reported by: | Owned by: | Dave Cole | |
---|---|---|---|
Priority: | high | Component: | CustomRoadmapPlugin |
Severity: | normal | Keywords: | |
Cc: | hju@… | Trac Release: | 0.11 |
Description
I have configured a custom workflow and try to get the customroadmap plugin to work. please check the attached screenshots.
Attachments (2)
Change History (13)
Changed 17 years ago by
Attachment: | roadmap_in_FireFox.png added |
---|
comment:1 Changed 16 years ago by
I had the same problem. You can work around this by editing the roadmap.css file in the default trac htdocs/css directory. Mine was located here: /usr/lib/python2.4/site-packages/Trac-0.11-py2.4.egg/trac/htdocs/css/roadmap.css
comment:2 Changed 16 years ago by
Priority: | normal → high |
---|
What are the modifications that I had to make in the roadmap.css file? Hope to hear a reply soon. thanks in advance!
comment:3 follow-up: 5 Changed 16 years ago by
There is a section that has a few "table.progress td" classes. Duplicate the td.new for each of your custom statuses. So if you have a "testing" status, you add the following:
table.progress td.testing { background: #[your color]}
comment:5 Changed 16 years ago by
Replying to dan@acucore.com:
There is a section that has a few "table.progress td" classes. Duplicate the td.new for each of your custom statuses. So if you have a "testing" status, you add the following:
table.progress td.testing { background: #[your color]}
Thanks! Worked perfectly.
comment:6 Changed 16 years ago by
Cc: | hu@… added; anonymous removed |
---|
facing the same problem.
You can work around this by editing the roadmap.css file in the default trac htdocs/css directory
...is a solution, but makes this Plugin useless. In this case I can use the Features in [milestone-groups] (since [0.11]) http://trac.edgewall.org/wiki/TracIni#milestone-groups-section to insert ticket states into progress bar.
Reason for the error seems to be #1867
comment:8 Changed 16 years ago by
This does not work for me either. I am running trac on windows. I attempted to update all the roadmap.css files I could find. yet still no change. Here are the lines from the displayed source. Note there are two references to roadmap.css.
<link rel="stylesheet" href="/rsm/chrome/common/css/trac.css" type="text/css" /><link rel="stylesheet" href="/rsm/customroadmap/roadmap.css" type="text/css" /><link rel="stylesheet" href="/rsm/chrome/theme/gnomebr.css" type="text/css" />
...
<link rel="stylesheet" type="text/css" href="/rsm/chrome/common/css/roadmap.css" />
</head>
looking at the tracd output
ip - - [timestamp] "GET /rsm/customroadmap/roadmap.css HTTP/1.1" 500 -
I'm not sure what error 500 means in this context. Is it "file not found"?
comment:9 Changed 15 years ago by
Strange behaviour is that color is rendered correctly if I define the Colors as:
[roadmap-groups] assigned.color = DarkKhaki assigned.counts = true assigned.status = assignedtestcase,assigneddefect,assignedenhancement,assignedtask,infoneeded closed.color = LightGreen closed.counts = true closed.status = closed
if I define color in the format #xxxxxx rendering fails.
Can someone else confirm this behaviour?
comment:10 Changed 13 years ago by
The problem seems to be that attempt to get chrome/common/css/roadmap.css always returns the template instead of actual file.
comment:11 Changed 12 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
The functionality of this plugin is available in the Trac core with 0.11. See CustomRoadmapPlugin for more details.
Roadmap as rendered in Firefox.