Modify

Opened 4 years ago

Closed 20 months ago

#7653 closed defect (fixed)

Not all matching tickets showing up in calendar

Reported by: hasienda Owned by: hasienda
Priority: normal Component: WikiTicketCalendarMacro
Severity: major Keywords: ticket query
Cc: rjollos, tojo Trac Release: 0.11

Description

While we went past ticket no. 116 in an application with WikiTicketCalendarMacro being part of the central collaboration information page, I noticed that new tickets no longer showed up on day of creation for unknown reasons.

After some research I know, they are still found by TicketQuery as it reports in DEBUG log output. But there is a relevant Trac configuration option in trac.ini':

[query]
items_per_page = 100

Higher values there will let the tickets in question show up again in the calendar view. This will definitely impose a limitation for Trac applications with high ticket creation rate.

Attachments (1)

macro.py.patch (792 bytes) - added by tojo 2 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 4 years ago by hasienda

  • Severity changed from normal to major
  • Status changed from new to assigned

Where to set the limit? Is it possible to effectively unset this temporarily, i.e. per TicketQuery call, to allow for keeping limit tight for other uses, where this limit should apply as well. And as a minor, but most irritating question: Why did I see it with ticket no. 117 while setup is items_per_page = 100? BTW, there are no deleted tickets in that application.

The effect is somewhat hard to spot, therefor most annoying. While you could increasing value of aforementioned config option quite easily, it is definitely desirable to get rid of that WikiTicketCalendarMacro limitation inherited from Trac without any trac.ini change. Changing trac.ini should be seen as a known workaround. Let's have a closer look, if there's another way out of this.

Changed 2 years ago by tojo

comment:2 Changed 2 years ago by tojo

  • Cc tojo added

My stab at fixing this problem: macro.py.patch. Elegant? No. Works? Yes

comment:3 Changed 2 years ago by tojo

Forgot to say that the patch is for the 0.12 branch

comment:4 Changed 2 years ago by hasienda

(In [11742]) WikiCalendarMacro: Really get all matching tickets, refs #7653.

Thanks to Tobias Johansson for pointing me into the right direction with his proposed patch for WikiTicketCalendarMacro 0.12 branch.

comment:5 Changed 2 years ago by hasienda

Please consider switching to the upstream code, because this is the current development stage, where all bug fixing and new code inclusion happens.

I'm very grateful, that you helped to close one of the few remaining tickets, that held the next generation of WikiCalendarMacro back from initial release.

comment:6 Changed 20 months ago by hasienda

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [12842]) WikiCalendarMacro: Releasing current, tested macro package as final product, closes #64, #578, #6636, #7564, #7653, #8818, #9568, #9718 and #9719.

After a long time one of the oldest Trac hacks (see changeset [53]) is united with its ambitious fork WikiTicketCalendarMacro for convenience. While maintaining separate wiki pages for both macros, upstream development continues together in the source:wikicalendarmacro/trunk branch.

Add Comment

Modify Ticket

Action
as closed The owner will remain hasienda.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.