Opened 17 years ago
Closed 16 years ago
#1100 closed defect (worksforme)
TracTags updates for latest trunk (0.11)?
| Reported by: | anonymous | Owned by: | Alec Thomas |
|---|---|---|---|
| Priority: | normal | Component: | TagsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | garyo@… | Trac Release: | 0.11 |
Description
TracTags doesn't work with the trunk (jan 15, 2007) anymore. Most of the macros fail, with this message:
'Formatter' object has no attribute 'chrome'
Some stuff works though, like the tags cloud. But there is no "Keywords" field on the ticket form, either. Is this plugin still being developed/supported? I'd be happy to help with it if needed, but I'm not an expert by any means on trac internals.
Attachments (0)
Change History (10)
comment:1 Changed 17 years ago by
| Component: | TracHacks → TagsPlugin |
|---|
comment:2 Changed 17 years ago by
| Status: | new → assigned |
|---|
0.11 is still a moving target. TracTags will be ported once Trac trunk stabilises.
comment:3 Changed 17 years ago by
| Cc: | garyo@… added; anonymous removed |
|---|
Glad to hear it's not dead at least!
I know 0.11 is not stable yet :-) but I would be happy to help work on porting TracTags. Is there a todo list yet? I filed another ticket about it today.
comment:5 follow-up: 6 Changed 17 years ago by
Just want to ping this ticket again; it's the one thing holding us back from using trac 0.11 trunk. We need tags! :-) AThomas, do you feel like the extension API has started to stabilize enough to do this work? Again, I'll be glad to help when the time comes (I'm not a trac expert but I'm a decent python hacker).
comment:6 Changed 17 years ago by
Replying to garyo@genarts.com:
Just want to ping this ticket again; it's the one thing holding us back from using
i agree with garyo@…. seems trac's trunk is stable.
comment:7 Changed 17 years ago by
| Summary: | TracTags updates for latest trunk? → TracTags updates for latest trunk (0.11)? |
|---|
comment:9 Changed 17 years ago by
Definitely! I'm using it on the trunk r5925 (August 8th) with no problems at all. AThomas updated it just before that date to make it work with the 0.11 API. I've heard a refactoring recently went into the trunk though, which may break it again; I'm happy where I am for now so haven't tested it against recent trunk builds.
Correcting component.