hi Elemental,
Yes, I modified my File extension too (v3.1.1)
If you search for the following in ext.mh_file_ext.php: (should be around line 550):
// =============================================
// Add Field Data to $_POST
// =============================================
$r.= '<input type="hidden" name="field_id_'.$row['field_id'].'" value="'.htmlentities($field_data).'" />';
Then insert this line after it:
$r .= $DSP->input_hidden("field_ft_" . $row['field_id'], "none");
That should do the trick hopefully 😊
hi Elemental, Yes, I modified my File extension too (v3.1.1) If you search for the following in ext.mh_file_ext.php: (should be around line 550):Then insert this line after it:// ============================================= // Add Field Data to $_POST // ============================================= $r.= '<input type="hidden" name="field_id_'.$row['field_id'].'" value="'.htmlentities($field_data).'" />';
That should do the trick hopefully 😊$r .= $DSP->input_hidden("field_ft_" . $row['field_id'], "none");
Thanks! This is perfect. I am still using Mark Huot’s Multi Text extension so I threw the same code in there, too.
//
// Publish Tab
//
function publish( $row, $field_data )
{
global $DB, $DSP, $EXT;
$r = "";
$r .= $DSP->input_hidden("field_ft_" . $row['field_id'], "none");
There is an article at devot:ee about the field formatting issue that applies to this.
Any older add-on that creates a custom field type is prone to have these issues.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.