From ef61509dc2b2a4e2d29551402646c2a73cc6ee0d Mon Sep 17 00:00:00 2001
From: Neil Blakey-Milner <nbm@knowledgetree.com>
Date: Tue, 25 Apr 2006 13:44:18 +0000
Subject: [PATCH] KTS-888: don't show information about lookup fields on "normal" fields.

---
 templates/ktcore/metadata/editField.smarty | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/templates/ktcore/metadata/editField.smarty b/templates/ktcore/metadata/editField.smarty
index 2a4aa71..7231315 100644
--- a/templates/ktcore/metadata/editField.smarty
+++ b/templates/ktcore/metadata/editField.smarty
@@ -1,8 +1,5 @@
 <h2>{i18n}Edit Field{/i18n}: {$oField->getName()|escape}</h2>
 
-<p class="descriptiveText">{i18n}Lookup fields may have be composed of an arbitrary number of values. These values may be added to the Lookup field by entering them in below. If these values are being generated by, or synchronised to, an external datasource, toggling the <strong>Sticky</strong> attribute of a value will ensure that it will not be modified by changes in the external datasource list.{/i18n}</p> 
-
-
 <form action="{$smarty.server.PHP_SELF}" method="POST">
 <fieldset>
 <legend>{i18n}Field properties{/i18n}</legend>
@@ -34,6 +31,8 @@
 {assign var="aEnabledMetadata" value=$oField->getEnabledValues()}
 {assign var="aDisabledMetadata" value=$oField->getDisabledValues()}
 
+<p class="descriptiveText">{i18n}Lookup fields may be composed of an arbitrary number of values. These values may be added to the Lookup field by entering them in below. If these values are being generated by, or synchronised to, an external datasource, toggling the <strong>Sticky</strong> attribute of a value will ensure that it will not be modified by changes in the external datasource list.{/i18n}</p> 
+
 <h2>{i18n}Lookup Values{/i18n}</h2>
 
 <form action="{$smarty.server.PHP_SELF}" method="POST">
--
libgit2 0.21.4