Skip to content

Commit

Permalink
Item9693: Typo in DataForms. <nop> should not be visible
Browse files Browse the repository at this point in the history
  • Loading branch information
gac410 committed Jun 29, 2015
1 parent 5787c88 commit fa51a01
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions core/data/System/DataForms.txt
@@ -1,4 +1,4 @@
%META:TOPICINFO{author="ProjectContributor" date="1434988360" format="1.1" version="1"}%
%META:TOPICINFO{author="ProjectContributor" date="1435550482" format="1.1" version="1"}%
%META:TOPICPARENT{name="UserDocumentationCategory"}%
%STARTINCLUDE%
---+!! Data Forms
Expand Down Expand Up @@ -121,7 +121,7 @@ The name of the form field.
* You can space out the title of the field, and it will still find the topic e.g. =Aeroplane Manufacturers= is equivalent to =AeroplaneManufacturers=.
* If a =label= field has no name, it will *not* be shown when the form is *viewed*, only when it is *edited*.
* Field names can in theory include any text, but you should stick to alphanumeric characters. If you want to use a non-wikiname for a =select=, =checkbox= or =radio= field, and want to get the values from another topic, you can use =[<nop>[...]]= double bracket links. This notation can also be used when referencing another topic to obtain field values, but a name other than the topic name is required as the name of the field.
* If you want the Field name to include embedded spaces, use the format =[&lt;nop&gt;[FieldName][Descriptive human-friendly Field Name]]=.
* If you want the Field name to include embedded spaces, use the format =[<nop>[FieldName][Descriptive human-friendly Field Name]]=.
* Leading and trailing spaces do not matter.


Expand Down

0 comments on commit fa51a01

Please sign in to comment.