KF #7, all over the map. Up to page 158
This commit is contained in:
Colin Kuskie
parent
200b85f6ce
commit
5bda08209f
25 changed files with 111 additions and 128 deletions
|
|
@ -71,11 +71,6 @@ our $HELP = {
|
|||
description => '86 description',
|
||||
namespace => 'Asset_DataForm',
|
||||
},
|
||||
{
|
||||
title => '76',
|
||||
description => '76 description',
|
||||
namespace => 'Asset_DataForm',
|
||||
},
|
||||
],
|
||||
related => [
|
||||
{
|
||||
|
|
|
|||
|
|
@ -43,10 +43,6 @@ our $HELP = {
|
|||
},
|
||||
],
|
||||
related => [
|
||||
{
|
||||
tag => 'asset fields',
|
||||
namespace => 'Asset'
|
||||
},
|
||||
]
|
||||
},
|
||||
|
||||
|
|
|
|||
|
|
@ -51,8 +51,8 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'url help' => {
|
||||
message => q|The URL that this ad will link to. Note that this won't be used for Rich Media ads.|,
|
||||
lastUpdated => 0,
|
||||
message => q|The URL to which this ad will link. Note that this won't be used for Rich Media ads.|,
|
||||
lastUpdated => 1165511641,
|
||||
context => q|help for a form property in the ad editor|
|
||||
},
|
||||
|
||||
|
|
@ -218,8 +218,8 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'name help' => {
|
||||
message => q|This string is used in combination with the AdSpace macro to place ads on the site. It should contain no spaces and only alpha-numeric chracters.|,
|
||||
lastUpdated => 0,
|
||||
message => q|This string is used in combination with the AdSpace macro to place ads on the site. It should contain no spaces and only alpha-numeric characters.|,
|
||||
lastUpdated => 1165511561,
|
||||
context => q|help for a form property in the ad manager|
|
||||
},
|
||||
|
||||
|
|
|
|||
|
|
@ -407,8 +407,8 @@ a URL will be made from the parent's URL and the <b>Menu Title</b>.</p>|,
|
|||
},
|
||||
|
||||
'extra head tags description' => {
|
||||
message => q|<p>These tags will be added to the <head> section of each page that the asset appears on.</p>|,
|
||||
lastUpdated => 1126471216,
|
||||
message => q|<p>These tags will be added to the <head> section of each page on which the asset appears.</p>|,
|
||||
lastUpdated => 1165510986,
|
||||
},
|
||||
|
||||
'make package description' => {
|
||||
|
|
|
|||
|
|
@ -39,8 +39,8 @@ our $I18N = {
|
|||
lastUpdated => 1133619940
|
||||
},
|
||||
'dashboard add/edit body' => {
|
||||
message => q|<p>The dashboard is a container asset that acts like a portal. When in Admin mode, the dashboard admin is actually editing the Visitor's (default) view. When not in admin mode, the dashboard admin is editing their own personalized view. Shortcuts are the main source of functionality for the Dashboard. See the Shortcut add/edit documentation for details.</p><p><b>NOTE:</b> Due to limitations in Internet Explorer the dashboard does not work well with XHTML Strict compliance enabled. Therefore your style templates for dashboard pages should not be XHTML Strict. The other way to get around this problem is to ensure that when using XHTML Strict compliance, make sure that neither your does not constrain the dashboard inside of a div tag with a width attached to it.</p>|,
|
||||
lastUpdated => 1142888566
|
||||
message => q|<p>The dashboard is a container asset that acts like a portal. When in Admin mode, the dashboard admin is actually editing the Visitor's (default) view. When not in admin mode, the dashboard admin is editing their own personalized view. Shortcuts are the main source of functionality for the Dashboard. See the Shortcut add/edit documentation for details.</p><p><b>NOTE:</b> Due to limitations in Internet Explorer the dashboard does not work well with XHTML Strict compliance enabled. Therefore, your style templates for dashboard pages should not be XHTML Strict. The other way to get around this problem is to ensure that when using XHTML Strict compliance, make sure that you do not constrain the dashboard inside of a div tag with a width attached to it.</p>|,
|
||||
lastUpdated => 1165510892
|
||||
},
|
||||
'dashboard template field label' => {
|
||||
message => q|Dashboard Template|,
|
||||
|
|
|
|||
|
|
@ -14,8 +14,8 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'mail attachments description' => {
|
||||
message => q|Must be used in conjuction with 'Mail Data'. Setting to yes will cause all files submitted via the file field type to be mailed as attachments.|,
|
||||
lastUpdated => 0,
|
||||
message => q|Must be used in conjunction with 'Mail Data'. Setting to yes will cause all files submitted via the file field type to be mailed as attachments.|,
|
||||
lastUpdated => 1165511233,
|
||||
context => 'description of wobject property',
|
||||
},
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ functions.</p>
|
|||
message => q|<p>If set to yes, some additional fields will be added to your form for dealing with email. These fields will then be used to email any data entered into the form to a person of your choice. By default the new fields are "Hidden" so that
|
||||
they can't be edited by the user.</p>
|
||||
<p>
|
||||
<b>NOTE:</b> The "To" field that is added as a result of setting this to yes can accept a standard email address, or a WebGUI username or a WebGUI group name. To send an email to more than one address, separate them by commas.</p>|,
|
||||
<b>NOTE:</b> The "To" field that is added as a result of setting this to yes can accept a standard email address, a WebGUI username or a WebGUI group name. To send an email to more than one address, separate them by commas.</p>|,
|
||||
lastUpdated => 1146763307,
|
||||
},
|
||||
|
||||
|
|
@ -104,9 +104,9 @@ they can't be edited by the user.</p>
|
|||
|
||||
'defaultView description' => {
|
||||
message => q|Select the default view for the Data Form, either Form view (the default) or
|
||||
List view. When List view is selected, no acknowledgement will be displayed
|
||||
List view. When List view is selected, no acknowledgment will be displayed
|
||||
after data is entered in the form.|,
|
||||
lastUpdated => 1119071072,
|
||||
lastUpdated => 1165511134,
|
||||
},
|
||||
|
||||
'744' => {
|
||||
|
|
@ -116,8 +116,8 @@ after data is entered in the form.|,
|
|||
|
||||
'744 description' => {
|
||||
message => q|After creating the Data Form, you can either begin to add fields to it
|
||||
or return to the page where the it was created.|,
|
||||
lastUpdated => 1132354848,
|
||||
or return to the page where it was created.|,
|
||||
lastUpdated => 1165511258,
|
||||
},
|
||||
|
||||
'76 description' => {
|
||||
|
|
@ -136,7 +136,7 @@ or return to the page where the it was created.|,
|
|||
},
|
||||
|
||||
'76 description' => {
|
||||
message => q|Export the data from the Data Form in tab deliniated format.|,
|
||||
message => q|Export the data from the Data Form in tab delineated format.|,
|
||||
lastUpdated => 1119071072,
|
||||
},
|
||||
|
||||
|
|
@ -473,8 +473,8 @@ unless the user can edit the Data Form (<b>canEdit</b> it true).|,
|
|||
},
|
||||
|
||||
'tab.subtext' => {
|
||||
message => q|A description of this tab that can explain more the tab contents than the label.|,
|
||||
lastUpdated => 1149392054,
|
||||
message => q|A description of this tab that can explain more about the tab contents than the label.|,
|
||||
lastUpdated => 1165511090,
|
||||
},
|
||||
|
||||
'tab.controls' => {
|
||||
|
|
@ -549,8 +549,8 @@ below to see which template variables may be used inside this loop.|,
|
|||
},
|
||||
|
||||
'field_loop' => {
|
||||
message => q|A loop containing all of the field information. From outside the <b>field_loop</b> it's also possible to access all form fields directly. To accomplish this you should use these variables. Call them with <b>field.noloop.<i>fieldName</i>.<i>property</i></b>, where fieldName is the name of the field (not the label) and property is anyone of the properties supplied by the <b>field_loop</b>. If you want the form tag of field 'name' you should use <b>field.noloop.name.form</b> anywhere in your template. If you want to know if the field is required use <b>field.noloop.name.isRequired</b>.|,
|
||||
lastUpdated => 1149392054,
|
||||
message => q|A loop containing all of the field information. From outside the <b>field_loop</b> it's also possible to access all form fields directly. To accomplish this you should use these variables. Call them with <b>field.noloop.<i>fieldName</i>.<i>property</i></b>, where fieldName is the name of the field (not the label) and property is any one of the properties supplied by the <b>field_loop</b>. If you want the form tag of field 'name' you should use <b>field.noloop.name.form</b> anywhere in your template. If you want to know if the field is required use <b>field.noloop.name.isRequired</b>.|,
|
||||
lastUpdated => 1165511043,
|
||||
},
|
||||
|
||||
'field.form' => {
|
||||
|
|
@ -733,7 +733,7 @@ below to see which template variables may be used inside this loop.|,
|
|||
},
|
||||
|
||||
'record.submissionDate.epoch' => {
|
||||
message => q|The epoch datestamp for this record entry.|,
|
||||
message => q|The epoch date stamp for this record entry.|,
|
||||
lastUpdated => 1149392138,
|
||||
},
|
||||
|
||||
|
|
|
|||
|
|
@ -416,8 +416,8 @@ our $I18N = { ##hashref of hashes
|
|||
},
|
||||
|
||||
'checkout.url' => {
|
||||
message => q|A URL to take the user the screen that displays the contents of their shopping cart.|,
|
||||
lastUpdated => 1149828278,
|
||||
message => q|A URL to take the user the screen that displays the contents of the shopping cart.|,
|
||||
lastUpdated => 1165517333,
|
||||
},
|
||||
|
||||
'checkout.label' => {
|
||||
|
|
@ -456,8 +456,8 @@ our $I18N = { ##hashref of hashes
|
|||
},
|
||||
|
||||
'manageEvents.label' => {
|
||||
message => q|An internationalized label to dispaly to the user the link for managing events.|,
|
||||
lastUpdated => 1149828278,
|
||||
message => q|An internationalized label to display to the user the link for managing events.|,
|
||||
lastUpdated => 1165511492,
|
||||
},
|
||||
|
||||
'managePurchases.url' => {
|
||||
|
|
@ -466,17 +466,17 @@ our $I18N = { ##hashref of hashes
|
|||
},
|
||||
|
||||
'managePurchases.label' => {
|
||||
message => q|An internationalized label to dispaly to the user the link for managing purchases.|,
|
||||
lastUpdated => 1149828278,
|
||||
message => q|An internationalized label to display to the user the link for managing purchases.|,
|
||||
lastUpdated => 1165511507,
|
||||
},
|
||||
|
||||
'template help body' => {
|
||||
message => q|
|
||||
<p>This template is used to style the main page of the Event Management System where
|
||||
products are displayed to the user as well as providing a link for managing events
|
||||
products are displayed to the user as well as provide a link for managing events
|
||||
in the system.</p>
|
||||
|,
|
||||
lastUpdated => 1149828856,
|
||||
lastUpdated => 1165517304,
|
||||
},
|
||||
|
||||
'event template help title' => {
|
||||
|
|
@ -490,8 +490,8 @@ in the system.</p>
|
|||
},
|
||||
|
||||
'title.url' => {
|
||||
message => q|A URL to display a list of events that have this event|,
|
||||
lastUpdated => 1149828404,
|
||||
message => q|A URL to display a list of events that contain this event|,
|
||||
lastUpdated => 1165513731,
|
||||
},
|
||||
|
||||
'description' => {
|
||||
|
|
@ -540,8 +540,8 @@ in the system.</p>
|
|||
},
|
||||
|
||||
'eventIsFull' => {
|
||||
message => q|A boolean that is true if the there are no available seats remaining in this event.|,
|
||||
lastUpdated => 1149828404,
|
||||
message => q|A boolean that is true if there are no available seats remaining in this event.|,
|
||||
lastUpdated => 1165517259,
|
||||
},
|
||||
|
||||
'eventIsApproved' => {
|
||||
|
|
@ -677,8 +677,8 @@ the user can manage their purchases.</p>
|
|||
},
|
||||
|
||||
'registrationId' => {
|
||||
message => q|The user's registrationId for this event.|,
|
||||
lastUpdated => 1149828601,
|
||||
message => q|The user's registration Id for this event.|,
|
||||
lastUpdated => 1165511539,
|
||||
},
|
||||
|
||||
'templateId' => {
|
||||
|
|
@ -822,8 +822,8 @@ by setting the "hide" form variable.|,
|
|||
},
|
||||
|
||||
'addEvent.label' => {
|
||||
message => q|An internationalized label to dispaly to the user the link for adding an event.|,
|
||||
lastUpdated => 1149828900,
|
||||
message => q|An internationalized label to display to the user the link for adding an event.|,
|
||||
lastUpdated => 1165511512,
|
||||
},
|
||||
|
||||
'message' => {
|
||||
|
|
@ -1334,8 +1334,8 @@ normal templates.|,
|
|||
},
|
||||
|
||||
'associated user description' => {
|
||||
message => q|It is possible to link up this registrant with a user from the WebGUI user database and to synchronize their registrant information with their WebGUI profile. You may also create a new WebGUI user with their profile information started with their registrant information.|,
|
||||
lastUpdated => 1147050958,
|
||||
message => q|It is possible to link up this registrant with a user from the WebGUI user database and to synchronize their registrant information with their WebGUI profile. Alternately, you can create a new WebGUI user. If you do this, the new User's profile will be initially populated with their registrant information.|,
|
||||
lastUpdated => 1165512195,
|
||||
},
|
||||
|
||||
'badge id' => {
|
||||
|
|
|
|||
|
|
@ -19,11 +19,11 @@ our $I18N = {
|
|||
'file add/edit body' => {
|
||||
message => q|<p>File Assets are files on your site that are available for users to download. If you would like to have multiple files available, try using a FilePile Asset.</p>
|
||||
|
||||
<p>Since Files are Assets, so they have all the properties that Assets do. Below are the properties that are specific to Image Assets:</p>
|
||||
<p>Since Files are Assets, they have all the properties of Assets. Below are the properties that are specific to Image Assets:</p>
|
||||
|
||||
|,
|
||||
context => 'Describing file add/edit form specific fields',
|
||||
lastUpdated => 1119068839,
|
||||
lastUpdated => 1165517702,
|
||||
},
|
||||
|
||||
'file template title' => {
|
||||
|
|
@ -107,8 +107,8 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'new file description' => {
|
||||
message => q|Enter the path to a file, or use the "Browse" button to find a file on your local hard drive that you would like to be uploaded.|,
|
||||
lastUpdated => 1119068745
|
||||
message => q|Enter the path to a file, or use the "Browse" button to find a file on your local hard drive that you would like to be upload.|,
|
||||
lastUpdated => 1165517718
|
||||
},
|
||||
|
||||
};
|
||||
|
|
|
|||
|
|
@ -7,9 +7,9 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'file pile add/edit body' => {
|
||||
message => q|<p>File Pile Assets allow you to upload lots of files to your site all at once. This is the only function that File Piles have. If you want to display the files that have been uploaded, you'll need to use another Asset or Wobject.</p>
|
||||
message => q|<p>File Pile Assets allow you to upload lots of files to your site all at once. This is the only function that the File Pile has. If you want to display the files that have been uploaded, you'll need to use another Asset or Wobject.</p>
|
||||
|
||||
<p>Unlike most Assets, File Piles do not share the base set of Asset properties. All File Piles
|
||||
<p>Unlike most Assets, the File Pile does not share the base set of Asset properties. All File Piles
|
||||
have the following properties:</p>
|
||||
|
||||
|,
|
||||
|
|
@ -28,12 +28,6 @@ have the following properties:</p>
|
|||
lastUpdated => 1119214815,
|
||||
},
|
||||
|
||||
'108 description' => {
|
||||
message => q|<p>The owner of a page is usually the person who created the page. This user always has full edit and viewing rights on the page.
|
||||
</p>|,
|
||||
lastUpdated => 1119214815,
|
||||
},
|
||||
|
||||
'872 description' => {
|
||||
message => q|<p>Choose which group can view this page. If you want both visitors and registered users to be able to view the page then you should choose the "Everybody" group.
|
||||
</p>|,
|
||||
|
|
@ -97,11 +91,11 @@ have the following properties:</p>
|
|||
},
|
||||
|
||||
'108 description' => {
|
||||
message => q|<p>The owner of a asset is usually the person who created the asset. This user always has full edit and viewing rights on the asset.
|
||||
message => q|<p>The owner of an asset is usually the person who created the asset. This user always has full editing and viewing rights on the asset.
|
||||
</p>
|
||||
<p> <b>NOTE:</b> The owner can only be changed by an administrator.
|
||||
</p>|,
|
||||
lastUpdated => 1119149899,
|
||||
lastUpdated => 1165517660,
|
||||
},
|
||||
|
||||
'872' => {
|
||||
|
|
|
|||
|
|
@ -2,15 +2,15 @@ package WebGUI::i18n::English::Asset_HttpProxy;
|
|||
|
||||
our $I18N = {
|
||||
'use ampersand help' => {
|
||||
message => q|By default we use semicolons to seperate parameters in a URL. However, some older applications require the use of ampersands.|,
|
||||
message => q|By default we use semicolons to separate parameters in a URL. However, some older applications require the use of ampersands.|,
|
||||
context => q|asset property hover help|,
|
||||
lastUpdated => 0
|
||||
lastUpdated => 1165517983
|
||||
},
|
||||
|
||||
'use ampersand' => {
|
||||
message => q|Use ampersand as seperator?|,
|
||||
message => q|Use ampersand as separator?|,
|
||||
context => q|asset property|,
|
||||
lastUpdated => 0
|
||||
lastUpdated => 1165517982
|
||||
},
|
||||
|
||||
'cache timeout description' => {
|
||||
|
|
|
|||
|
|
@ -99,13 +99,13 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'In Out Template description' => {
|
||||
message => q|Choose a template to style the display of the In/Out Board to users.|,
|
||||
lastUpdated => 1138988640,
|
||||
message => q|Choose a template to display the In/Out Board to users.|,
|
||||
lastUpdated => 1165518044,
|
||||
},
|
||||
|
||||
'13 description' => {
|
||||
message => q|Choose a template to style the display of the In/Out Board Report.|,
|
||||
lastUpdated => 1138988640,
|
||||
message => q|Choose a template to display the In/Out Board Report.|,
|
||||
lastUpdated => 1165518045,
|
||||
},
|
||||
|
||||
'3 description' => {
|
||||
|
|
@ -171,13 +171,13 @@ can alter their status.|,
|
|||
},
|
||||
|
||||
'deptHasChanged' => {
|
||||
message => q|A boolean value indicating whether or not this row of data is for a department that is differnet than the previous rows|,
|
||||
lastUpdated => 1149393667,
|
||||
message => q|A boolean value indicating whether or not this row of data is for a department that is different than the previous rows|,
|
||||
lastUpdated => 1165518086,
|
||||
},
|
||||
|
||||
'username' => {
|
||||
message => q|A variable that returns the users name. If the first and last name fields are defined in the user profile, that is what is returned. Otherwise, the users WebGUI username is returned. i.e., "John Doe" vs "Jdoe"|,
|
||||
lastUpdated => 1149393667,
|
||||
message => q|A variable that returns the user's name. If the first and last name fields are defined in the user profile, that is what is returned. Otherwise, the user's WebGUI username is returned. i.e., "John Doe" vs "Jdoe"|,
|
||||
lastUpdated => 1165518097,
|
||||
},
|
||||
|
||||
'status' => {
|
||||
|
|
|
|||
|
|
@ -146,8 +146,8 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'email.wasSent' => {
|
||||
message => q|A condition indicating whether an email message was sent or not.|,
|
||||
lastUpdated => 1149784175,
|
||||
message => q|A condition indicating whether or not an email message was sent.|,
|
||||
lastUpdated => 1165518551,
|
||||
},
|
||||
|
||||
'edit.url' => {
|
||||
|
|
|
|||
|
|
@ -437,8 +437,8 @@ from working.|,
|
|||
},
|
||||
|
||||
'form.dependants' => {
|
||||
message => q|Form element for something I really don't understand.|,
|
||||
lastUpdated => 1149825164,
|
||||
message => q|Form element for entering in which task this task depends on, by number.|,
|
||||
lastUpdated => 1165512623,
|
||||
},
|
||||
|
||||
'form.resource' => {
|
||||
|
|
|
|||
|
|
@ -610,10 +610,10 @@ expression. The regex you enter here should be perl style.</p>|,
|
|||
},
|
||||
|
||||
'no field types message' => {
|
||||
message => q|In order to add fields to a SQLForm field types
|
||||
message => q|In order to add fields to an SQLForm field types
|
||||
must be defined. Currently there are no field types defined, and therfore it is
|
||||
not possible ta add fields. Please add at least one field type by going to|,
|
||||
lastUpdated => 0,
|
||||
lastUpdated => 1165517851,
|
||||
},
|
||||
|
||||
'manage field types title' => {
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ SQL Reports are Wobjects and Assets, so they share the properties of both. SQL
|
|||
},
|
||||
|
||||
'Placeholder Parameters description' => {
|
||||
message => q|<p>Placeholders, also called parameter markers, are used to indicate values in a SQL query that will be supplied later, before the statement is executed.</p>
|
||||
message => q|<p>Placeholders, also called parameter markers, are used to indicate values in an SQL query that will be supplied later, before the statement is executed.</p>
|
||||
<p>There are four input types:</p>
|
||||
<div>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -590,8 +590,8 @@ Usually the RDN looks something like:</p>
|
|||
},
|
||||
|
||||
'6 description' => {
|
||||
message => q|The LDAP Identity is the unique identifier in the LDAP server that the user will be identified against. Often this field is <b>shortname</b>, which takes the form of first initial + last name. Example: jdoe. Therefore if you specify the LDAP identity to be <i>shortname</i> then Jon Doe would enter <i>jdoe</i> during the registration process.|,
|
||||
lastUpdated => 1120164594,
|
||||
message => q|The LDAP Identity is the unique identifier in the LDAP server that the user will be identified against. Often this field is <b>shortname</b>, which takes the form of first initial + last name. Example: jdoe. Therefore, if you specify the LDAP identity to be <i>shortname</i> then Jon Doe would enter <i>jdoe</i> during the registration process.|,
|
||||
lastUpdated => 1165512076,
|
||||
},
|
||||
|
||||
'7 description' => {
|
||||
|
|
@ -628,8 +628,8 @@ Usually the RDN looks something like:</p>
|
|||
},
|
||||
|
||||
'login template description' => {
|
||||
message => q|Template used to display login information to the user as an operation as opposed to inside of a page via a macro.|,
|
||||
lastUpdated => 1120164594,
|
||||
message => q|Template used to display login information to the user as an operation, as opposed to inside of a page via a macro.|,
|
||||
lastUpdated => 1165512102,
|
||||
},
|
||||
|
||||
'ldap connection add/edit body' => {
|
||||
|
|
|
|||
|
|
@ -327,8 +327,8 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'help manage pending transactions body' => {
|
||||
message => q|<p>All transactions that are marked as 'Pending' are listed here. Transactions are marked pending if some extra review is required. For instance when a transaction is suspected of fraud. Pending transactions can also be transactions that yet have to be confirmed by something as or similar to PayPal's APN. If you have checked that the transaction is legit you can click on the 'Complete transaction' link.</p>|,
|
||||
lastUpdated => 1101772650,
|
||||
message => q|<p>All transactions that are marked as 'Pending' are listed here. Transactions are marked pending if some extra review is required. For instance when a transaction is suspected of fraud. Pending transactions can also be transactions that have yet to be confirmed by something as or similar to PayPal's APN. If you have checked that the transaction is legit you can click on the 'Complete transaction' link.</p>|,
|
||||
lastUpdated => 1165518203,
|
||||
context => q|The body of the help page of the list pending transactions screen.|
|
||||
},
|
||||
|
||||
|
|
|
|||
|
|
@ -16,11 +16,11 @@ our $I18N = {
|
|||
message => q|
|
||||
|
||||
<p><b>^FormParam();</b><br />
|
||||
This macro is mainly used in generating dynamic queries in SQL Reports. Using this macro you can pull the value of any form field simply by specifying the name of the form field, like this: ^FormParam("phoneNumber");
|
||||
This macro is mainly used in generating dynamic queries in SQL Reports. Using this macro, you can pull the value of any form field simply by specifying the name of the form field, like this: ^FormParam("phoneNumber");
|
||||
</p>
|
||||
<p>If the macro is used to pull data from a form field that returns multiple values, like a dropdown list, then only the first value will be returned.</p>
|
||||
|,
|
||||
lastUpdated => 1154143837,
|
||||
lastUpdated => 1165517791,
|
||||
},
|
||||
};
|
||||
|
||||
|
|
|
|||
|
|
@ -57,12 +57,12 @@ our $I18N = {
|
|||
message => q|<p>WebGUI macros are used to create dynamic content within otherwise static content. For instance, you may wish to show which user is logged in on every page, or you may wish to have a dynamically built menu or crumb trail.
|
||||
</p>
|
||||
|
||||
<p>Macros always begin with a caret (^) and follow with at least one other character and ended with a semicolon (;). Some macros can be extended/configured by taking the format of <b>^x</b>("<i>config text</i>");. When providing multiple arguments to a macro, they should be separated by only commas:<br />
|
||||
<p>Macros always begin with a caret (^) and follow with at least one other character and end with a semicolon (;). Some macros can be extended/configured by taking the format of <b>^x</b>("<i>config text</i>");. When providing multiple arguments to a macro, they should be separated by only commas:<br />
|
||||
<b>^x</b>(<i>"First argument",2</i>);
|
||||
</p>
|
||||
|
||||
|,
|
||||
lastUpdated => 1146608624,
|
||||
lastUpdated => 1165518386,
|
||||
},
|
||||
|
||||
'topicName' => {
|
||||
|
|
|
|||
|
|
@ -228,11 +228,10 @@ our $I18N = {
|
|||
'help list products body' => {
|
||||
message => q|<span style="font-weight: bold;">Overview</span><br />
|
||||
<br />
|
||||
Next to subscriptions WebGUI features products. Product allow you to
|
||||
In addition to subscriptions, WebGUI features products. Products allow you to
|
||||
sell your products with considerable ease. Just define a base product
|
||||
and add parameters to it if you need to. WebGUI generates all possible
|
||||
product configuration for you and sets the price, weight and sku values
|
||||
according to your wishes automatically.<br />
|
||||
product configurations for you and automatically sets the price, weight and sku values.<br />
|
||||
<br />
|
||||
For example you want to sell T-shirts in the sizes S, M, L and XL and
|
||||
the colors blue and grey. Also an XL costs $ 1.50 extra. <br />
|
||||
|
|
@ -246,7 +245,7 @@ Now you have created eight variants of your T-shirt product and only in
|
|||
about a minute. <br />
|
||||
<br />
|
||||
If you are out of blue large T-shirts, just disable this variant. You
|
||||
are in full controll.<br />
|
||||
are in full control.<br />
|
||||
<br />
|
||||
<span style="font-weight: bold;">Usage</span><br />
|
||||
<br />
|
||||
|
|
@ -319,7 +318,7 @@ of your product.
|
|||
Products consist of base Properties along with Parameters with various
|
||||
Options. The properties are the base of your product. They define the
|
||||
the default price, weight, sku and sku composition of the product and
|
||||
all it's variants.
|
||||
all its variants.
|
||||
</p>
|
||||
|
||||
<p><b>Properties</b><br />
|
||||
|
|
@ -367,11 +366,11 @@ The delete button left of an option allows you to delete that option.
|
|||
<p><b>List variants</b><br />
|
||||
This menu option can be found in the righthand side menu, and allows
|
||||
you to view all product variants that are possible with the given
|
||||
options. Also this is the place to change the automatically generated
|
||||
options. Also, this is the place to change the automatically generated
|
||||
price, weight and sku values and set availability of a product variant.
|
||||
</p>
|
||||
|,
|
||||
lastUpdated => 1146606324,
|
||||
lastUpdated => 1165518436,
|
||||
context => q|The body of the manage product help page|
|
||||
},
|
||||
|
||||
|
|
@ -448,9 +447,8 @@ default weight for product variants consisting of this option.</p>|,
|
|||
},
|
||||
|
||||
'edit option sku modifier description' => {
|
||||
message => q|<p>The value that the template variable of
|
||||
the parameter this is an option of in the SKU template takes.</p>|,
|
||||
lastUpdated => 1122609417,
|
||||
message => q|<p>When this option is called in the SKU template as a template variable, the value that will be displayed.</p>|,
|
||||
lastUpdated => 1165513384,
|
||||
},
|
||||
'help list variants title' => {
|
||||
message => q|List product variants|,
|
||||
|
|
@ -460,9 +458,9 @@ the parameter this is an option of in the SKU template takes.</p>|,
|
|||
'help list variants body' => {
|
||||
message => q|<span style="font-weight: bold;">Overview</span><br />
|
||||
<br />
|
||||
Product variants are that what customers can actually buy. This screen
|
||||
Product variants are what customers can actually buy. This screen
|
||||
shows all possible configurations of parameters and options and
|
||||
therfore define the product variants you can actually sell.<br />
|
||||
therefore define the product variants you can actually sell.<br />
|
||||
<span style="font-weight: bold;"></span><br />
|
||||
<span style="font-weight: bold;">The variant list<br />
|
||||
</span><br />
|
||||
|
|
@ -486,9 +484,10 @@ at the bottom and the top of the screen.<br />
|
|||
Also you can edit variants to override their automatically generated
|
||||
values for price, weight and SKU. To do this simply click on the edit
|
||||
button next to the variant you want to edit.<br />|,
|
||||
lastUpdated => 0,
|
||||
lastUpdated => 1165518232,
|
||||
context => q|The body of the list variants help page|
|
||||
},
|
||||
|
||||
'help edit variant title' => {
|
||||
message => q|Edit product variant|,
|
||||
lastUpdated => 0,
|
||||
|
|
@ -515,18 +514,18 @@ Please note that a field containing only spaces is not empty.</p>
|
|||
},
|
||||
|
||||
'price override description' => {
|
||||
message => q|Here you can set the price for this variant.|,
|
||||
lastUpdated => 1146607100,
|
||||
message => q|The price for this variant.|,
|
||||
lastUpdated => 1165513644,
|
||||
},
|
||||
|
||||
'weight override description' => {
|
||||
message => q|Here you can set yhe weight of this variant.|,
|
||||
lastUpdated => 1146607101,
|
||||
message => q|The weight of this variant.|,
|
||||
lastUpdated => 1165513603,
|
||||
},
|
||||
|
||||
'sku override description' => {
|
||||
message => q|Here you can set the SKU of this variant.|,
|
||||
lastUpdated => 1146607102,
|
||||
message => q|The SKU of this variant.|,
|
||||
lastUpdated => 1165513642,
|
||||
},
|
||||
|
||||
'available description' => {
|
||||
|
|
|
|||
|
|
@ -9,9 +9,9 @@ our $I18N = {
|
|||
|
||||
'html template expr body' => {
|
||||
message => q|<p>HTML Template Expr is an extension to HTML Template that adds expressions to the language. <a href="http://search.cpan.org/perldoc?HTML%3A%3ATemplate%3A%3AExpr">Documentation for this extension</a> is available online.</p>
|
||||
<p>The syntax of template variables in HTML Template Expr is slightly different from HTML Template. Any WebGUI template variables that contains a dot '.', should be chanaged to use an underscore instead '_'.</p>
|
||||
<p>The syntax of template variables in HTML Template Expr is slightly different from HTML Template. Any WebGUI template variables that contains a dot '.', should be changed to use an underscore instead '_'.</p>
|
||||
|,
|
||||
lastUpdated => 1162085513,
|
||||
lastUpdated => 1165517942,
|
||||
context => q|Explanation of HTML Template Expr usage in WebGUI.|
|
||||
},
|
||||
|
||||
|
|
|
|||
|
|
@ -339,8 +339,8 @@ our $I18N = {
|
|||
'manage version tags body' => {
|
||||
message => q|<p>This screen lists all uncommitted version tags in WebGUI, their status and an interface to manage them. If you are currently working under a tag, the name of the tag is prominently displayed for reference.</p>
|
||||
<p>The icons next to each tag allow each tag to be edited, or deleted. The name of the tag is a link to manage work done in the tag. The date the tag was created and the username of the user who created are shown as well. A link is provided so that the tag can be committed</p>
|
||||
<p>Links are also provided to set any version tag that is not your version tag your new current working version tag. From that point forward, all work will be done under the new tag.</p>|,
|
||||
lastUpdated => 1148359381,
|
||||
<p>Links are also provided to set any other version tag as your new current working version tag. From that point forward, all work will be done under the new tag.</p>|,
|
||||
lastUpdated => 1165518479,
|
||||
},
|
||||
|
||||
'manage pending versions body' => {
|
||||
|
|
|
|||
|
|
@ -1555,14 +1555,13 @@ sent in HTML format. No attachments can be included.|,
|
|||
},
|
||||
|
||||
'620' => {
|
||||
message => q|<p>As this function suggests you'll be deleting a group and removing all users from the group. Be careful not to restrict users from pages they should have access to by deleting a group that is in use.
|
||||
message => q|<p>As this function suggests, you'll be deleting a group and removing all users from the group. Be careful not to restrict users from pages they should have access to by deleting a group that is in use.
|
||||
</p>
|
||||
|
||||
<p>As with any delete operation, you are prompted to be sure you wish to proceed with the delete. If you answer yes, the delete will proceed and there is no recovery possible. If you answer no you'll be returned to the prior screen.
|
||||
</p>
|
||||
|
||||
|,
|
||||
lastUpdated => 1100154599
|
||||
lastUpdated => 1165517903
|
||||
},
|
||||
|
||||
'1004' => {
|
||||
|
|
@ -1840,7 +1839,7 @@ sent in HTML format. No attachments can be included.|,
|
|||
},
|
||||
|
||||
'1005 description' => {
|
||||
message => q|<p>Many organizations have external databases that map users to groups; for example an HR database might map Employee ID to Health Care Plan. To validate users against an external database, you need to construct a SQL statement that will return the list of WebGUI userIds for users in the group. You may use macros in this query to access data in a user's WebGUI profile, such as Employee ID. Here is an example that checks a user against a fictional HR database. This assumes you have created an additional WebGUI profile field called employeeId.</p>
|
||||
message => q|<p>Many organizations have external databases that map users to groups; for example an HR database might map Employee ID to Health Care Plan. To validate users against an external database, you need to construct an SQL statement that will return the list of WebGUI userIds for users in the group. You may use macros in this query to access data in a user's WebGUI profile, such as Employee ID. Here is an example that checks a user against a fictional HR database. This assumes you have created an additional WebGUI profile field called employeeId.</p>
|
||||
<p>
|
||||
select userId from employees, health_plans, empl_plan_map<br />
|
||||
where employees.employee_id = ^User("employeeId");<br />
|
||||
|
|
@ -1851,7 +1850,7 @@ and health_plans.health_plan_id = empl_plan_mp.health_plan_id<br />
|
|||
<p>
|
||||
This group could then be named "Employees in HMO 1", and would allow you to restrict any page or wobject to only those users who are part of this health plan in the external database.
|
||||
</p>|,
|
||||
lastUpdated => 1146592080,
|
||||
lastUpdated => 1165517843,
|
||||
},
|
||||
|
||||
'1004 description' => {
|
||||
|
|
@ -3791,9 +3790,9 @@ Select which of the configured LDAP connections to use to authenticate users.
|
|||
},
|
||||
|
||||
'content filter body' => {
|
||||
message => q|<p>WebGUI has many features to accept content from outside sources, such as users posting to message boards or pulling data from external websites via the HttpProxy or SyndicatedContent Assets. However, this can expose pose a risk to your site, for example, through cross-site scripting attacks.</p>
|
||||
message => q|<p>WebGUI has many features to accept content from outside sources, such as users posting to message boards or pulling data from external websites via the HttpProxy or SyndicatedContent Assets. However, this can expose a risk to your site, for example, through cross-site scripting attacks.</p>
|
||||
<p>To help solve this problem
|
||||
many Assets have a <b>^International("418","WebGUI");</b> property that performs various leveling
|
||||
many Assets have a <b>^International("418","WebGUI");</b> property that performs various levels
|
||||
of filtering on content. Each one is pretty self-explanatory:</p>
|
||||
<div>
|
||||
<dl>
|
||||
|
|
@ -3811,7 +3810,7 @@ JavaScript fields from HTML tags.</dd>
|
|||
<dd>Strips everything that it can, returning just plain old, safe text.</dd>
|
||||
</dl></div>
|
||||
|,
|
||||
lastUpdated => 1113681314,
|
||||
lastUpdated => 1165517754,
|
||||
},
|
||||
|
||||
'glossary title' => {
|
||||
|
|
@ -3959,8 +3958,8 @@ Message Boards hold forums for users. There are many different Wobjects in WebG
|
|||
},
|
||||
|
||||
'allowed keywords description' => {
|
||||
message => q|You can enter the statements that are allowed for this databaselink. A safe (read-only) choice is SELECT, DESCRIBE and SHOW. The different keywords should be seperated from each other by whitespace.|,
|
||||
lastUpdated => 0,
|
||||
message => q|You can enter the statements that are allowed for this databaselink. A safe (read-only) choice is SELECT, DESCRIBE and SHOW. The different keywords should be separated from each other by whitespace.|,
|
||||
lastUpdated => 1165511447,
|
||||
},
|
||||
|
||||
'preview' => {
|
||||
|
|
|
|||
|
|
@ -74,9 +74,9 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'description help' => {
|
||||
message => q|Fill out a detailed description of what this workflow does and is used for for future reference.|,
|
||||
message => q|Fill out a detailed description of what this workflow does and what it is used for for future reference.|,
|
||||
context => q|the hover help for the description field|,
|
||||
lastUpdated => 0,
|
||||
lastUpdated => 1165513695,
|
||||
},
|
||||
|
||||
'description' => {
|
||||
|
|
|
|||
|
|
@ -110,9 +110,9 @@ our $I18N = {
|
|||
},
|
||||
|
||||
'priority help' => {
|
||||
message => q|This determines the priority level of the workflow to be executed. Normally this should be left at "medium". If the workflow needs urgent execcution, then set it to "high". If it's a maintenance task and can be put off until the server is less busy, then set it to "low"|,
|
||||
message => q|This determines the priority level of the workflow to be executed. Normally this should be left at "medium". If the workflow needs urgent execution, then set it to "high". If it's a maintenance task and can be put off until the server is less busy, then set it to "low"|,
|
||||
context => q|the hover help for the priority|,
|
||||
lastUpdated => 0,
|
||||
lastUpdated => 1165510791,
|
||||
},
|
||||
|
||||
'priority' => {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue