Skip Menu |

This queue is for tickets about the RT-Extension-HistoryFilter CPAN distribution.

Report information
The Basics
Id: 89670
Status: resolved
Priority: 0/
Queue: RT-Extension-HistoryFilter

People
Owner: CLOOS [...] cpan.org
Requestors: CMCKAY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.03
Fixed in: 1.00



Subject: Broken in 4.2.0
Hi, In RT 4.2.0 They've made ShowHistory an asynchronous call and moved its html thingy from share/html/Ticket/Elements/ShowHistory to share/html/Elements/ShowHistory So subsequently your callback never gets called because your path no longer lines up. Fix is to move your callback element from local/plugins/RT-Extension-HistoryFilter/html/Callbacks/HistoryFilter/Ticket/Elements/ShowHistory/SkipTransaction to local/plugins/RT-Extension-HistoryFilter/html/Callbacks/HistoryFilter/Elements/ShowHistory/SkipTransaction To maintain backwards compatibility I'd suggest installing to both paths so both cases are covered. I haven't tested the presence of the new file location against a 4.0.17 installation, but it doesn't look like it would collide with anything to cause any side effects. Thanks, -Chris
Hi Chris, thanks for the suggested fix. I released version 1.00 which is now also compatible with RT 4.2. Chris Am Di 22. Okt 2013, 02:20:32, CMCKAY schrieb: Show quoted text
> Hi, > > In RT 4.2.0 They've made ShowHistory an asynchronous call and moved > its html thingy > from share/html/Ticket/Elements/ShowHistory > to share/html/Elements/ShowHistory > So subsequently your callback never gets called because your path no > longer lines up. > > Fix is to move your callback element > from local/plugins/RT-Extension- > HistoryFilter/html/Callbacks/HistoryFilter/Ticket/Elements/ShowHistory/SkipTransaction > to local/plugins/RT-Extension- > HistoryFilter/html/Callbacks/HistoryFilter/Elements/ShowHistory/SkipTransaction > > To maintain backwards compatibility I'd suggest installing to both > paths so both cases are covered. I haven't tested the presence of the > new file location against a 4.0.17 installation, but it doesn't look > like it would collide with anything to cause any side effects. > > Thanks, > -Chris