Modify ↓
Opened 10 years ago
Last modified 10 years ago
#11988 new defect
trac-jsgantt versus trac-jsGantt
Reported by: | jvbussel | Owned by: | Chris Nelson |
---|---|---|---|
Priority: | normal | Component: | TracJsGanttPlugin |
Severity: | normal | Keywords: | trac.ini |
Cc: | Trac Release: |
Description
we are using the trac ini-editor to offer the posibility to change ini settings using the web interface. This plugin reports the sections trac-jsgantt and trac-jsGantt. I had a look in the sourcecode and saw both section names. Can all section names be written as trac-jsgantt or trac-jsGantt? We are using Linux to host Trac and are therefore case sensitive.
Further the section TracPM is detected but no options are beeing reported.
Attachments (0)
Change History (2)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Writing them the same in the code everywhere would be great. A quick grep turned out that it is probably just one typo
./tracjsgantt/tracjsgantt.py: Option('trac-jsGantt', 'option.linkStyle', 'standard',
Note: See
TracTickets for help on using
tickets.
Replying to joop.van.bussel@…:
I don't know if the configuration processing in Trac (or Python?) is case sensitive. The plugin code uses trac-jsgantt in all but one place (I should fix that). It is likely safest to use all lower case.
I'm not sure what to make of that. I'm not familiar with the ini editor you refer to. There certainly can be values in that section. I'd have to think to see if they are all optional. The plugin code uses "TracPM" consistently.
Mine configuration looks like
there are examples on the plugin's page.