[rt-users] RT 3.4.2 custom fields defaulting to value '1'

[Jason Parsons]

On Aug 2, 2005, at 15:07 , Jason Parsons wrote:

>
> After upgrading RT from 3.4.1 to 3.4.2, I'm finding that "enter one  
> value" and "select one value" custom fields are defaulting to a  
> value of '1' (instead of empty).  For example, I have a "select one  
> value" transaction custom-field called 'severity', with values:  
> 'normal', 'urgent', or '(no value)'.  When '(no value)' is  
> selected, and the transaction is saved, the transaction displays  
> with a severity of '1' (which is obviously bogus).

With a bit more debugging, it does appear that this is a problem on  
the update side.  Saving a note from Update.html without touching the  
custom fields yields these sql queries:

INSERT INTO ObjectCustomFieldValues (ContentType, LargeContent,  
CustomField, Creator, ObjectId, LastUpdatedBy, Disabled, Created,  
Content, ContentEncoding, LastUpdated, ObjectType) VALUES (NULL,  
NULL, '1', '94', '10568', '94', '0', '2005-08-04 02:31:30', '1', '',  
'2005-08-04 02:31:30', 'RT::Transaction')

INSERT INTO ObjectCustomFieldValues (ContentType, LargeContent,  
CustomField, Creator, ObjectId, LastUpdatedBy, Disabled, Created,  
Content, ContentEncoding, LastUpdated, ObjectType) VALUES (NULL,  
NULL, '2', '94', '10568', '94', '0', '2005-08-04 02:31:30', '1', '',  
'2005-08-04 02:31:30', 'RT::Transaction')

Note that 'Content' is being set to '1'.

I haven't been able to track down where this is happening.

  - Jason Parsons