fixing misspelled word separate in all help files
This commit is contained in:
parent
b18853b866
commit
fedc7b33a7
3 changed files with 8 additions and 8 deletions
|
|
@ -1043,8 +1043,8 @@ have been purged yet.</p>|,
|
|||
'completeForm' => {
|
||||
message => q|This contains the entire form, complete
|
||||
and layed out in a WebGUI-style table. You don't need to add a
|
||||
seperate form header, footer or anything else.|,
|
||||
lastUpdated => 1149822620,
|
||||
separate form header, footer or anything else.|,
|
||||
lastUpdated => 1167186643,
|
||||
},
|
||||
|
||||
'formLoop' => {
|
||||
|
|
@ -1163,7 +1163,7 @@ automatically, using a default layout.</p>
|
|||
<p><b>formloop</b> handles placing everything that you need in a table,
|
||||
automatically. This allows you some flexibility in your form layout.</p>
|
||||
<p>Finally there is the option of placing
|
||||
each seperate field by hand. This allows you to define the order and
|
||||
each separate field by hand. This allows you to define the order and
|
||||
place of each form element. Please note, however, that using this
|
||||
method will not automatically follow changes you make to the SQLForm.
|
||||
If you add, delete or rename a field you must update the template by
|
||||
|
|
@ -1171,7 +1171,7 @@ hand. Using this method also implies the use of <b>formHeader</b> and
|
|||
<b>formFooter.</b> You should use the following two template
|
||||
variables:</p>
|
||||
|,
|
||||
lastUpdated => 1149822668,
|
||||
lastUpdated => 1167186648,
|
||||
},
|
||||
|
||||
'search template help title' => {
|
||||
|
|
|
|||
|
|
@ -316,8 +316,8 @@ query, but will be prefixed with queryN where N goes from 2 to 5.</p>
|
|||
'Prequery statements description' => {
|
||||
message => q|<p>Prequery statements are sql statements executed before the real query. You can use prequery statements for instance to set variables that you want to use in the real query. For example:</p>
|
||||
<div class="helpIndent">set @myVariable := 1</div>
|
||||
<p>The prequery statements are seperated from each other by returns and cannot use placeholders. You can use macro's within the prequery statements, however. Please note that prequery statements are only visible in the query they belong to and that you can only use statements that are allowed by the database link.</p>|,
|
||||
lastUpdated => 0,
|
||||
<p>The prequery statements are separated from each other by returns and cannot use placeholders. You can use macro's within the prequery statements, however. Please note that prequery statements are only visible in the query they belong to and that you can only use statements that are allowed by the database link.</p>|,
|
||||
lastUpdated => 1167186661,
|
||||
},
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -26,9 +26,9 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'to help' => {
|
||||
message => q|The email address to send the message to. You may put in mutliple email addresses seperated by commas.|,
|
||||
message => q|The email address to send the message to. You may put in multiple email addresses separated by commas.|,
|
||||
context => q|the hover help for the to field|,
|
||||
lastUpdated => 0,
|
||||
lastUpdated => 1167186609,
|
||||
},
|
||||
|
||||
'to' => {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue