I just tested this with URL field extension
$r .= $DSP->input_hidden('field_ft_'.$row['field_id'],$row['field_fmt']);
and can confirm that it works fine.
It seems that upon creation of a custom field, the formatting definition works fine and gets stores in the database (the value form the drop down). It’s just being ignores upon entry creation without the hidden format value.
This does not solve your problem Ryan, but it sure solved the problem of custom fields having no formatting set after 1.6.5 upgrade.
However, you still need to make sure that the formatting is being set in the first place through the hook
publish_admin_edit_field_extra_row
otherwise you’ll get this error, as the format will default to NULL
Description: Unknown column ‘field_ft_7’ in ‘field list’
EDIT: It seems that you don’t need the formatting drop-down when creating a custom field. Without it, it should default to ‘none’.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.