oqapi/webgui
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

KF edits up to page 287

Browse source
This commit is contained in:
Colin Kuskie 2006-12-27 02:38:41 +00:00
parent fedc7b33a7
commit 9c629bf79c
7 changed files with 16 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

4
lib/WebGUI/i18n/English/Asset.pm
View file

@ -84,8 +84,8 @@ our $I18N = {
},
'purge trash after help' => {
message => q|How long should an asset stay in the trash before it's considered old enough to purge? Note that when it get's purged all it's revisions and descendants will be purged as well.|,
lastUpdated => 0,
message => q|How long should an asset stay in the trash before it's considered old enough to purge? Note that when it gets purged all it's revisions and descendants will be purged as well.|,
lastUpdated => 1167187074,
context => q|the hover help for the purge trash after field|
},

4
lib/WebGUI/i18n/English/Asset_Product.pm
View file

@ -513,8 +513,8 @@ our $I18N = {
},
'41' => {
message => q|Features are selling points for a product. IE: Reasons to buy your product. Features often result in benefits, so you may want to also add some benefits to this product.|,
lastUpdated => 1120335841
message => q|Features are selling points for a product(ie. reasons to buy your product). Features often result in benefits, so you may want to also add some benefits to this product.|,
lastUpdated => 1167186992
},
'58' => {

4
lib/WebGUI/i18n/English/Asset_RichEdit.pm
View file

@ -413,8 +413,8 @@ option is set to Yes, then all whitespace entered into the form will be preserve
},
'use br description' => {
message => q|Uses break tags <BR> instead of paragraph tags <P> when a newline is entered in the editor.|,
lastUpdated => 1119584875,
message => q|Uses break tags <BR> instead of paragraph tags <P> when a new line is entered in the editor.|,
lastUpdated => 1167187299,
},
'remove line breaks description' => {

6
lib/WebGUI/i18n/English/Asset_SQLReport.pm
View file

@ -17,14 +17,14 @@ our $I18N = {
},
'71' => {
message => q|<p>SQL Reports are perhaps the most powerful wobject in the WebGUI arsenal. They allow a user to query data from any database that they have access to. This is great for getting sales figures from your Accounting database or even summarizing all the message boards on your web site.</p>
message => q|<p>SQL Reports are perhaps the most powerful wobject in the WebGUI arsenal. They allow a user to query data from any database that they have access to. This is great for getting sales figures from your accounting database or even summarizing all the message boards on your web site.</p>
<p><b>Nested query support</b><br />
The SQL Report wobject supports up to 5 nested queries (1 base query and 4 subqueries). Each subsequent query is executed for each row in the previous query results. For example, if you have two queries: query1 and query2, then query2 will be executed once for each row returned in query1. You can use placeholder parameters to compose subqueries with data from prior queries.
The SQL Report wobject supports up to 5 nested queries (1 base query and 4 subqueries). Each subsequent query is executed for each row in the previous query results. For example, if you have two queries (query1 and query2), then query2 will be executed once for each row returned in query1. You can use placeholder parameters to compose subqueries with data from prior queries.
</p>
<p>
SQL Reports are Wobjects and Assets, so they share the properties of both. SQL Reports also have these unique properties:
</p>|,
lastUpdated => 1146785522,
lastUpdated => 1167187342,
},
'72 description' => {

4
lib/WebGUI/i18n/English/Macro_RandomAssetProxy.pm
View file

@ -17,10 +17,10 @@ our $I18N = {
<p><b>&#94;RandomAssetProxy</b>();<br />
<b>&#94;RandomAssetProxy</b>(<i>Asset URL</i>);<br />
This macro works similarly to the &#94;<b>AssetProxy</b>(); macro except instead of displaying the
Asset, it picks a random Asset from the descendents of the Asset whose URL is supplied as the
Asset, it picks a random Asset from the descendants of the Asset whose URL is supplied as the
argument.</p>
|,
lastUpdated => 1146760545,
lastUpdated => 1167187099,
},
'childless' => {

6
lib/WebGUI/i18n/English/Macro_RandomThread.pm
View file

@ -15,7 +15,7 @@ our $I18N = {
'random thread body' => {
message => q|<p><b>&#94;RandomThread( [ startURL, relatives, templateURL ] );</b><br />
The Collaboration System can be used for much more than just a forum. A few examples of its
possible usages are a FAQ, photo gallery, job listings, quotes database or weblog. For these
possible usages are an FAQ, photo gallery, job listings, quotes database or weblog. For these
applications (and others that you might think of) it can be nice to display a random entry
from such a CS somewhere on your site. That is exactly the functionality that this macro provides.</p>
@ -24,7 +24,7 @@ depending on the parameters. The way the selected post is displayed is controlle
the template variables that are normally available in a CS Post template are available in this macro as well.</p>
<p><b>Parameters</b></p>
<p>Although all the parameters can be omitted, it usually makes sense specify them all. If you
<p>Although all the parameters can be omitted, it usually makes sense to specify them all. If you
want to display a random thread from a single CS, we suggest you use the URL of the CS as the <i>startURL</i>
and &quot;self&quot; as <i>relatives</i>.</p>
<div>
@ -63,7 +63,7 @@ of questions), then the example above can be used to display a random question f
</dl>
</div>
|,
lastUpdated => 1146760592,
lastUpdated => 1167187168,
},
};

4
lib/WebGUI/i18n/English/Workflow_Activity_ProcessRecurringPayments.pm
View file

@ -9,8 +9,8 @@ our $I18N = {
},
'process recurring payments body' => {
message => q|<p>This workflow activity will process all recurring transactions (payments) in the Commerce system that are complete at the time the Activity is executed. When the Activity is through with all those payments, a email with the details of all transactions is sent to the user configured in the Settings to receive them.</p>|,
lastUpdated => 0,
message => q|<p>This workflow activity will process all recurring transactions (payments) in the Commerce system that are complete at the time the Activity is executed. When the Activity is through with all those payments, an email with the details of all transactions is sent to the user configured in the Settings to receive them.</p>|,
lastUpdated => 1167186902,
},
};