Any clues appreciated. I have no idea how to start debugging code in a Genshi template.
(Confirmation that I'm not the only one seeing weird custom field placement would be nice, too.) On Mon, Oct 29, 2012 at 10:39 AM, Christopher Nelson <[email protected]> wrote: > (I sent this last week and the body disappeared. Sorry.) > > I have a gazillion plugins installed in a Trac 0.11.6 installation and > I'm seeing strange ordering of custom fields. I've seen this before > but didn't bother to look into it but I'm adding another field now and > can't get it to go where I want it and it's making me crazy. (It's > broken the same way in three different installations here.) > > At first I thought the problem might be due to > TimingAndEstimationPlugin (http://trac-hacks.org/ticket/10547) because > the Hours field seems to trigger it but that doesn't seem to be so. > There is a conversation there that eliminates some wrong answers, > though. > > I'm using TimingAndEstimationPlugin 1.2.7 with MasterTickets, > Subtickets, EstimationTools and other plugins and I'm seeing strange > behavior with regard to how custom fields are displayed. > > A ticket type with no custom fields has 8 standard fields at the top: > > Reporter Owner > Priority Milestone > Component Version > CC Keywords > > My custom fields are ordered: > > estimatedhours 0 > confidence 1 > blockedby 2 > blocking 3 > build 4 > hours 5 > totalhours 6 > customer 7 > defectcause 8 > supplier_name 9 > supplier_id 10 > supplier_pn 11 > supplier_contact 12 > userfinish 13 > parents 14 > > If I add in estimatedhours, a locally-defined field (confidence), and > blockedby, and blocking, they are after Keywords: > > Reporter Owner > Priority Milestone > Component Version > CC Keywords > Estimated Hours Confidence > Depends On Required For > > When I add hours, it gets added *before* keywords: > > Reporter Owner > Priority Milestone > Component Version > CC <empty place for hidden hours> > Keywords Estimated Hours > Confidence Depends On > Required For > > then a few fields continue being added after hours, before keywords > then the addition resumes at the end of the custom fields. I > eventually end up with: > > Reporter Owner > Priority Milestone > Component Version > CC Build > <empty> Total Hours > Keywords Estimated Hours > Confidence Depends On > Required For Due Date > Parent Ticket > > As far as I can tell ticket/api.py returns all fields sorted, standard > first, custom second (in order) and nothing else sorts them. I can > barely spell Genshi so I have no idea how to add instrumentation to > tickets/template/ticket.html to log how fields are being processed > there. Any advice on isolating this problem? Has anyone else had > similar problems? -- A: Top-posting. Q: What is the most annoying thing in e-mail? -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
