[rt-users] Re: [Rt-devel] Errors with cascading select fields in RT 3.6.0

[Timothy Smith]

I've attached a two-line patch against the 3.6.0 release of lib/RT/Interface/Web.pm that addresses the cascading custom field issues described below.

Tim Smith
Office of Compliance

>>> "Timothy Smith" <tsmith at loc.gov> 06/19/06 3:08 PM >>>
Hello all. I've upgraded from RT 3.4.5 to 3.6.0 (clean install directory but the same database; custom patches applied) and I'm having some issues with the cascading select custom fields.

Assume a category "foo" has values "bar" and "baz" in it.

Ticket creation:
If I specify category foo and then select either bar or baz, RT gets confused and displays "foo" as the value of the field in Display.html. This does not happen in a different custom field in a different queue. Are things being processed out of order somewhere? I think CreateTicket in Interface/Web.pm might be getting confused by the -Category field; it doesn't check for the string Value in the name of the field.

Ticket updating (cosmetic):
RT always throws the error:
>> User asked for an unknown update type for custom field Testfield for RT::Ticket object
when I submit Ticket/Modify.html for a ticket with a cascading selector. It's coming from ProcessObjectCustomFieldUpdates in Interface/Web.pm; it looks like it's just missing an elsif to handle the -Category form field.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cascades.diff
Type: application/octet-stream
Size: 924 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20060621/69887818/attachment.obj>