Hello.
I wrote a RSS generator plugin (based on RT 3.0.5 but could work on
later version). It should be unpacked in the RT base directory, and will
put files in local/html/Search. Be warned that it will override standard
Listing.html.
It simply adds a link to a RSS generator in the Search page : set up
your search query then copy the target of the RSS link.
I tried it with Mozilla Firebird’s RSS Panel reader and found it quite
useful.
Notice that it requires authentication anyway so some tweaking is
required to use it from a automated processus (web content managment
tools or portals, like PHP-Nuke, etc…).
Regards,
Guillaume Perréal.
Responsable informatique,
Cemagref, groupement de Lyon,
France.
Tél: (+33) 4.72.20.87.87.
Fax: (+33) 4.78.47.78.75.
Site: http://www.lyon.cemagref.fr/
RSS-Search.tar.gz (2.39 KB)
Hello,
I’ve tried poking through the Ticket htm/mod_perl files, using cat as
well as grep’ing for keywords, however I think I can save some time by
asking here:
Where are the individual components for the display of a ticket
located? I’ve looked through /path/rt3/share/html Elements, Tickets,
etc.
I’m trying to hack mine to include some intelligence in the display of
elements. For example, we used “Custom Fields” to label product
groups. Obviously not every group is in every ticket, so I’m going to
include != (no value) so that undefined values don’t clutter up the
display of the ticket (we have about 7 product groups). Also, I’m going
to do the same with the “Dates”. “Not Set” doesn’t help me, so I’d like
it to just skip fields “not set”, undefined or further void of value.
Thanks!
If anyone is interested I’ll post my changes, but it should be just
simple if $whatever != undef yada yada yada.
John