RT 2.1.53 Custom Fields

Hello !

with your help i get RT 2.1.53 working :slight_smile: The new installation procedure
works for me.

The reason for testing the new RT 2.1.53 developement snapshot was to
evaluate the new custom field function. But when i create a freeform field
there is an error dispayed within the browser:

error: could not find component for path
’/Ticket/Elements/EditCustomFieldEntries’

context: …
41:
42: % }
43:
44: % if (@entry_fields) {
45: <& /Ticket/Elements/EditCustomFieldEntries, ReadOnly => 1,
CustomFields => @entry_fields, TicketObj => $Ticket &>
46: % }
47: <%INIT>
48: my $CustomFields = $Ticket->QueueObj->CustomFields();
49: </%INIT>
…

code stack: /opt/rt3/share/html/Ticket/Elements/ShowCustomFields:45
/opt/rt3/share/html/Ticket/Elements/ShowSummary:39
/opt/rt3/share/html/Ticket/Display.html:30
/opt/rt3/share/html/autohandler:151

Is this module not yet ready?

Thanks for your help!

Mit freundlichen Grᅵᅵen / Kind Regards
Stefan Fischer

Hi,

I haven’t had time to try the new version, but seems like the
bug is in the path spec:— Stefan Fischer info@debian.homeunix.net wrote:

45: <& /Ticket/Elements/EditCustomFieldEntries, ReadOnly => 1,
^^^^
shouldn’t it be one of existing files:

-rw-r–r-- 1 ssinyagi None 2096 Dec 2 01:07 EditCustomFieldValues
-rw-r–r-- 1 ssinyagi None 2456 Dec 2 01:07 EditCustomFields

Cheers,
Stan

Hi,

I haven’t had time to try the new version, but seems like the
bug is in the path spec:

Actually, no. It’s an accidental byproduct of a merge from
OurInternet’s branch of 2.1. It’ll get fixed for the next rev.

»|« http://www.bestpractical.com/rt – Trouble Ticketing. Free.