status limitations
stax - January 13, 2007 - 15:13
| Project: | Project issue tracking |
| Version: | 4.7.x-2.1 |
| Component: | Issues |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | duplicate |
Jump to:
Description
Hi,
it seems dealing with status has limitations and things are hardcoded, is it true that colors are hardcoded against status IDs? If so adding custom statuses and renaming statuses is kind of awkward. How can I define which statuses are shown by the default view? I want to use issues for my application StaxRip. Why is the status ID exposed at all?
Thanks
stax
#1
a) you're totally free to theme the status colors all you want. see project_issue.css for some details. however, all this CSS is *vastly* better in the version in HEAD for the 5.x port (not yet officially ready to release).
b) yes, certain status values are hard-coded, and it's lame. see the following older issues:
http://drupal.org/node/56200
http://drupal.org/node/27865
#2
Hi,
Thanks for the quick support and your work, I'm now satisfied with the system and my configuration hoping for a smooth upgrade path to Drupal 5.0.
cheers
stax