How does the cascading thing work? Is this using the Link feature in the
CF configuration page or is there a way of specifying sub-CFs of a CF?
PKFrom: rt-devel-bounces@lists.bestpractical.com
[mailto:rt-devel-bounces@lists.bestpractical.com] On Behalf Of
rt-devel-request@lists.bestpractical.com
Sent: 21 June 2006 09:00
To: rt-devel@lists.bestpractical.com
Subject: Rt-devel Digest, Vol 27, Issue 20
Send Rt-devel mailing list submissions to
rt-devel@lists.bestpractical.com
To subscribe or unsubscribe via the World Wide Web, visit
The rt-devel Archives
or, via email, send a message with subject or body ‘help’ to
rt-devel-request@lists.bestpractical.com
You can reach the person managing the list at
rt-devel-owner@lists.bestpractical.com
When replying, please edit your Subject line so it is more specific than
“Re: Contents of Rt-devel digest…”
Today’s Topics:
- Re: Errors with cascading select fields in RT 3.6.0
(Timothy Smith)
Message: 1
Date: Wed, 21 Jun 2006 09:08:55 -0400
From: “Timothy Smith” tsmith@loc.gov
Subject: Re: [Rt-devel] Errors with cascading select fields in RT
3.6.0
To: rt-devel@lists.bestpractical.com
Cc: rt-users@lists.bestpractical.com
Message-ID: s4990cc4.017@loc.gov
Content-Type: text/plain; charset=“us-ascii”
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@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-devel/attachments/20060621/9
c6319fb/cascades-0001.obj
Rt-devel mailing list
Rt-devel@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
End of Rt-devel Digest, Vol 27, Issue 20