[quote="Ethnar":2hcmlutv]Well, if simply moving it out of the tab and into the main part is what will suffice - add parameter 'extra'=>false to definition of the field.
If you really want to modify tpl - it's hell of a job, especially that you want this field as 3rd (not first, not last). I don't recommend that approach.[/quote:2hcmlutv]
In relation to what jaisek said, I am not intending to dive into the depth of templates and run modifications there, that is not what I want nor what I aim for.
And with regards to the 'extra'=>false attribute, that is not working, in the sense that, the field itself simply does not show at all in the contacts edit/view form.
I have tried this approach in my module's install() method:
Utils_RecordBrowserCommon::new_record_field('contact',
'Customer ID', 'text', true, true, null, null, false, false, null);
That doesn't show the field in the edit/view form of contacts but it does show it as the last field in the browsing (listing) mode, although clicking on it for sorting, just to see what happens, results in a database error.
Trying the array approach which I picked up from the actual function source code:
Utils_RecordBrowserCommon::new_record_field('contact',
array('name' => 'Customer ID', 'type' => 'text',
'extra' => false, 'required' => true, 'visible' => true));
results in the same behavior.
But, if I specify it like this, then it does work, meaning I see this field added in the form edit/view but it's placed at the very end, after the date of birth selection box:
Utils_RecordBrowserCommon::new_record_field('contact',
'Customer Number', 'text', true, true);
In anyway, regarding the placement of this field, the wiki clearly states that the position key show specify either in field name as string or in integer the point at which this field should be entered in the form, so I don't see why I would need to re-do the template when I am able to control fields position that way.
Regards,
Liran.
