Opened 12 years ago

Last modified 9 years ago

#9508 closed defect

Installation instructions result in non-working plugin — at Version 6

Reported by: Robert Inder Owned by: Chris Nelson
Priority: high Component: TracJsGanttPlugin
Severity: major Keywords:
Cc: Trac Release: 0.12

Description (last modified by Ryan J Ollos)

I am evaluating the TracJsGanttPlugin in Trac 0.12, in a test project with the following Plugins installed:

  • timingandestimationplugin-1.2.1b-py2.4.egg
  • TracMasterTickets-3.0.2-py2.4.egg
  • TracSubTicketsPlugin-0.1.0-py2.6.egg

To these I have added Trac_jsGantt-0.9-py2.4.egg following the "single project" installation instructions in the TracPlugins page at edgewall.org. I then enabled the plugin, and copied the [trac-jsgantt] configuration section into into the project's trac.ini file. I also ran trac-admin .... upgrade, which said that the database was up to date.

At this point, including [[TracJSGanttChart]] in a Wiki page produces a box containing the error message userstart is not a custom ticket field.

I tried adding "userstart" and "userfinish" to [ticket-custom], but this only changed the error message to unsupported operand type(s) for *: 'NoneType' and 'float'

What's gone wrong? None of the other plugins mention/define "userstart" and "userfinish", so I don't understand where they should be coming from...

Change History (6)

comment:1 Changed 12 years ago by falkb

What did you add for "userstart" and "userfinish" to ticket-custom? I have

userfinish = text
userfinish.label = Planned Finish
userfinish.order = 4
userfinish.value = 
userstart = text
userstart.label = Planned Start
userstart.order = 4
userstart.value = 

comment:2 Changed 12 years ago by Ryan J Ollos

The first error you mention is documented and a patch provided in #9445. The second error you mention is documented and some potential fixes described in #9441.

comment:3 in reply to:  1 Changed 12 years ago by anonymous

Replying to falkb:

What did you add for "userstart" and "userfinish" to ticket-custom?

I just put them in as

userfinish = text
userfinish.label = Planned Finish
userstart = text
userstart.label = Planned Start

But my worry is that I did that by guesswork: I didn't see anything in the installation instructions to say I had to do anything at all about them. Am I supposed to declare these for myself? Because when I do, I just get a different error. Or is the fact that they are missing a sign that something has gone wrong?

comment:4 Changed 12 years ago by Ryan J Ollos

You need to create custom ticket fields and then specify these fields in the trac-jsgantt section. For example,

[ticket-custom]
userfinish = text
userfinish.label = Planned Finish
userstart = text
userstart.label = Planned Start

[trac-jsgantt]
fields.start = userstart
fields.finish = userfinish

See t:TracTicketsCustomFields and TracJsGanttPlugin#Installation for more details. The installation instructions could probably be improved.

Howevever, #9441 will be a blocker for you unless you also define the estimate field, or make a change to the source code.

comment:5 Changed 12 years ago by Ryan J Ollos

I made some updates to TracJsGanttPlugin#Installation in response to the issues encountered in this ticket. Feedback welcome and appreciated.

comment:6 Changed 12 years ago by Ryan J Ollos

Description: modified (diff)
Note: See TracTickets for help on using tickets.