Opened 14 years ago
Closed 14 years ago
#7213 closed defect (fixed)
Wrong WikiTicketCalendar description
Reported by: | Jun Omae | Owned by: | Steffen Hoffmann |
---|---|---|---|
Priority: | normal | Component: | WikiTicketCalendarMacro |
Severity: | minor | Keywords: | 0.12 |
Cc: | Ryan J Ollos | Trac Release: | 0.12 |
Description
WikiTicketCalendar
macro doesn't work with the documentation issue.
-
wikiticketcalendar/macro.py
53 53 Activate it in 'trac.ini': 54 54 -------- 55 55 [components] 56 WikiTicketCalendarMacro.* = enabled56 wikiticketcalendar.* = enabled 57 57 58 58 Usage 59 59 -----
Attachments (0)
Change History (4)
comment:1 Changed 14 years ago by
Cc: | Ryan J Ollos added; anonymous removed |
---|---|
Owner: | changed from Ryan J Ollos to Steffen Hoffmann |
comment:2 Changed 14 years ago by
Keywords: | 0.12 added |
---|---|
Severity: | normal → minor |
Status: | new → assigned |
Trac Release: | 0.11 → 0.12 |
If enabled via Trac webadmin following line is added to trac.ini
wikiticketcalendar.macro.wikiticketcalendarmacro = enabled
So you're definitely right, that documentation is wrong for the 0.12 branch. This is old code I missed to adapt when rewriting the whole macro into packaged plugin. Since Trac will enable new plugins by default (at least it does so here in my development environment), in common use case this will not even noticed. But the old activation line is obsolete as well. I'll mention this on the wiki page too.
Thanks for reporting. This will be fixed with next maintenance release - tonight.
comment:3 Changed 14 years ago by
BTW, would be nice, if you'd mention the macro version next time. It was introduced exactly for that purpose. Thanks for taking care.
comment:4 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [8104]) WikiTicketCalendarMacro: Update source documentation on macro activation, closes #7213.
This was a left-over from the unpackaged versions. Thanks to Jun Omae for reporting and suggesting the correct fix.
The issue you report makes sense, although it appears you must be using the 0.12 version, not the 0.11 version as you report in the ticket.
I'll refer to hasienda on the issue since I haven't had time lately to keep up with his development.