Peter M. Groen / knowledgetree

Commit c1b9558e53c106995422cb05d40b5bdd777c1fa8

Authored by Neil Blakey-Milner
1 parent d1adc404

Rather don't put Generic and Type-Specific Metadata side-by-side, so 

that field size increases can be handled better.


git-svn-id: https://kt-dms.svn.sourceforge.net/svnroot/kt-dms/trunk@3332 c91229c3-7414-0410-bfa2-8a42b809f60b
Inline Side-by-side
Showing 1 changed file with 2 additions and 1 deletions
presentation/lookAndFeel/knowledgeTree/documentmanagement/addDocumentUI.inc
  View file @c1b9558
... ... @@ -130,7 +130,8 @@ function getMetaDataForm($iFolderID, $iDocumentTypeID) {
130 130 $oTypeSpecificPattern = getTypeSpecificMetaDataForm($iFolderID, $iDocumentTypeID);
131 131 $sToRender .= "<table border=\"0\" width=\"100%\">\n";
132 132 $sToRender .= "<tr><td><b>" . _("Document Meta Data") . "<b></td></tr>\n";
133   - $sToRender .= "<tr><td valign=\"top\">" . $oGenericPattern->render() . "</td><td valign=\"top\">" . $oTypeSpecificPattern->render() . "</td></tr>";
  133 + $sToRender .= "<tr><td valign=\"top\">" . $oGenericPattern->render() . "</td></tr>";
  134 + $sToRender .= "<tr><td valign=\"top\">" . $oTypeSpecificPattern->render() . "</td></tr>";
134 135 $sToRender .= "</table>";
135 136  
136 137 // validation starts
... ...