[rt-users] Can't coerce array into hash at /opt/rt3/sbin/../lib/RT/CustomField.pm line 696.

[Kevin Falcone]

On Thu, Jul 07, 2011 at 01:01:27PM -0700, Direct Insure Online wrote:
> Hi Kevin,
>  
> I deleted all *_Overlay.pm files when I upgraded and I have the following setting in RT_SiteConfig.pm
> Set(@Plugins, qw(
>                  RT::Authen::ExternalAuth
>                  RT::Extension::CustomField::Checkbox
>                 ));

Ah, there's the problem.

RT-Extension-CustomField-Checkbox has been superseded by RT4 (and in
fact is really incompatible with RT4).  Unfortunately, there isn't
currently an upgrade script, although we'll make sure this gets into
the bug tracker.

You *should* be able to do something like this in your development
environment.

Find the entry in your CustomFields table with the Checkbox entry,
update Type to Select and DisplayType to List.

-kevin

> If I comment the above one I am getting the following error
> could not find component for path 'EditCustomFieldSelectCheckbox' 
>  
> If I enable the above in RT_SiteConfig.pm I am getting the following error
> Can't coerce array into hash at /opt/rt3/sbin/../lib/RT/CustomField.pm line 696.
> Can't coerce array into hash at /opt/rt3/sbin/../lib/RT/CustomField.pm line 620.
> 
> With Regards
> Vinod.R
>  
> 
> From: Kevin Falcone <falcone at bestpractical.com>
> To: rt-users at lists.bestpractical.com
> Sent: Thursday, July 7, 2011 12:46 PM
> Subject: Re: [rt-users] Can't coerce array into hash at /opt/rt3/sbin/../lib/RT/CustomField.pm line 696.
> 
> On Thu, Jul 07, 2011 at 08:42:27AM -0700, Direct Insure Online wrote:
> >    We just upgraded our RT from 3.8.4 to 4.0.1
> >    We upgraded the database also.
> > 
> >    When we want to create a new custom field we are getting the following errors
> > 
> >    Can't coerce array into hash at /opt/rt3/sbin/../lib/RT/CustomField.pm line 696.
> >    Can't coerce array into hash at /opt/rt3/sbin/../lib/RT/CustomField.pm line 620.
> > 
> >    What could be the problem.
> 
> The most common failure for something like this is that you have a
> CustomField_Overlay.pm left over from 3.8 and didn't follow the
> directions.  Alternately, you might have a local customization or
> extension that affects Custom Fields.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110707/24a69d59/attachment.sig>