[ic] Admin UI code issue

[Mike Heins]

Quoting Thomas J.M. Burton (tom at globalfocusdm.com):
> Mike Heins wrote:
> > Quoting Mike Heins (mike at perusion.com):
> >   
> >> That being said, you could try supplying an overall_template option in
> >> the call to the table-editor, i.e. a custom pages/admin/flex_editor. Something
> >> like:
> >>
> >>     [table-editor
> >> 	    cgi=1
> >> 	    form_name=flex_editor
> >> 	    keep-errors=1
> >>     ]
> >> 	{TOP_OF_FORM}
> >> 	{HIDDEN_FIELDS}
> >> 	<table>
> >> 	<tr><td colspan="$span">{TOP_BUTTONS}</td></tr>
> >> 	<tr>
> >> 	    <td colspan="$span">
> >> 		    {:REST}
> >> 	    </td>
> >> 	</tr>
> >> 	<tr><td colspan="$span">{BOTTOM_BUTTONS}</td></tr>
> >> 	</table>
> >> 	{BOTTOM_OF_FORM}
> >>     [/table-editor]
> >>
> >> It has been a long time, so I can't be sure that is correct. You would have
> >> to refer to the source in all likelihood to completely nail it down.
> >>     
> >
> > And remember, you can copy the lib/UI/pages/include/templates/ui_type*
> > files to the catalog/include/templates directory and change those
> > markers there as well.
> >
> >   
> Hi again,
> 
> Just a little follow-up for the record. I copied the ui_type* files over 
> to the catalog's local level as you suggested and moved the markers in 
> ui_type1. So far so good, my DOM-modified fields are submitting and 
> there doesn't seem to be any malfunction in the rest of the form. If I 
> run into any problems resulting from this, I'll make another follow-up post.

Thanks for following up. I guess the templating turned out to be
suitable for it's purpose. I created this method, and the output_map
facility in Interchange, for exactly this type of scenario.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/
phone +1.765.328.4479  tollfree 800-949-1889 <mike at perusion.com>

Experience is what allows you to recognize a mistake the second
time you make it. -- unknown