hi,
how can i limit the queue-display.
i’ve now 10.000 of entries.
when i like to have a look at the resolved entries my netscape is
exploding;)
maby there’s a dirty quick hack before the new version.
robert
how can i limit the queue-display.
i’ve now 10.000 of entries.when i like to have a look at the resolved entries my netscape is
exploding;)maby there’s a dirty quick hack before the new version.
Somebody wrote a quick and dirty hack for it, but I don’t know if the
patch can be applied to the latest 1.0-code.
The problem with a quick hack is that the same select is made from the cli as
from the web ui, and the mail ui.
The quickest and dirtiest hack is to change rt/lib/database.pm line 199 as
follows:
amend ‘ORDER BY id"’ to read ‘ORDER BY id DESC LIMIT 100"’
This will only show the last 100 most recent requests. but this kinda renders
RT just barely useful. A less ugly, but more time consuming option would be to
create a new variable called display_limit_value, set by default to, maybe 50.
that line would then read ‘ORDER BY id DESC LIMIT $display_limit_value"’
Then you could add a filter (rt/lib/rt/ui/web/forms.pm) to change that value.
Then make sure that value is passed around to database.pm. Of course then,
you’d want to add an argument to the cli, otherwise you’d just get the default
number of reqs displayed from there too.
The other thing you could do, is edit the filters to disable listing of
resolved requests, thus stopping people crashing themselevs out. If people
need to look at a resolved request, and don’t know the ticket number, then
either use the cli and grep, or if the subject isn’t descriptive, try grep
-Ri ‘keyword’ whilst in rt/transactions/
I’d probably try hacking it myself, but I’m figuring a stable, stable RT v2.0
isn’t that far away, and I’ll just make do with RT’s eccentricities until then.
-Feargal.
Feargal Reilly,
Systems Administrator,
The CIA.
+353-86-8157621.