From cfece34eeb7097afa63e4ca1a82da9925a185600 Mon Sep 17 00:00:00 2001 From: Colin Kuskie Date: Thu, 7 Dec 2006 00:51:03 +0000 Subject: [PATCH] KF #6: Commerce, Commit Version Tag, Asset Toolbar, CS --- lib/WebGUI/i18n/English/Asset.pm | 14 +++++++------- lib/WebGUI/i18n/English/Asset_Collaboration.pm | 8 ++++---- lib/WebGUI/i18n/English/Commerce.pm | 10 +++++----- lib/WebGUI/i18n/English/VersionTag.pm | 2 +- .../English/Workflow_Activity_CacheEMSPrereqs.pm | 4 ++-- .../English/Workflow_Activity_CommitVersionTag.pm | 4 ++-- 6 files changed, 21 insertions(+), 21 deletions(-) diff --git a/lib/WebGUI/i18n/English/Asset.pm b/lib/WebGUI/i18n/English/Asset.pm index b4438ea28..40e757ee6 100644 --- a/lib/WebGUI/i18n/English/Asset.pm +++ b/lib/WebGUI/i18n/English/Asset.pm @@ -38,8 +38,8 @@ our $I18N = { }, 'confirm change url message' => { - message => q|Setting this to 'Yes' confirms that you want to permanently change this URL, thusly deleteing all old revisions of this asset.|, - lastUpdated => 0, + message => q|Setting this to 'Yes' confirms that you want to permanently change this URL, thus deleteing all old revisions of this asset.|, + lastUpdated => 1165449241, context => q|explains the implications of the change url function| }, @@ -61,7 +61,7 @@ our $I18N = { }, 'change url body' => { - message => q|

Suppose that you want to put a new Asset in the place of an old Asset and to use the old Asset's URL for the new Asset. Normally, to do this you would have to change the URL in the latest revision of the Asset and then purge each and every revision of the old Asset (since the old revisions of the old Asset have the same URL). Change URL allows you to do this easily. Enter in the new URL for the old Asset, and it will perform all the work for you.

|, + message => q|

Suppose that you want to put a new Asset in the place of an old Asset, but to use the old Asset's URL for the new Asset. Normally, to do this you would have to change the URL in the latest revision of the Asset and then purge each and every revision of the old Asset (since the old revisions of the old Asset have the same URL). Change URL allows you to do this easily. Enter in the new URL for the old Asset, and it will perform all the work for you.

|, lastUpdated => 0, }, @@ -609,7 +609,7 @@ each asset under the tab "Meta" in the asset properties.

contenttype = sport AND source != newspaper

You can use the AOI macro's described above in the criteria, so you can - present content based upon the users Areas of Interest. Example:
+ present content based upon the user's Areas of Interest. Example:
type = ^AOIRank(contenttype);

  • Display
    Metadata fields are exposed to the asset templates as their property name. So you can actually display the metadata @@ -619,7 +619,7 @@ each asset under the tab "Meta" in the asset properties.

    to create meta tags from meta data, including the tags from the Dublin Core standard.

    • |, context => q|Metadata help|, - lastUpdated => 1165356337 + lastUpdated => 1165450008 }, 'metadata edit property' => { @@ -888,8 +888,8 @@ Couldn't open %-s because %-s
    }, 'manage versions body' => { - message => q|

    This screen displays a list of all versions for the current Asset, showing the date it was committed or opened, who owns the tag for that version, and the name of the version tag. Icons will allow you purge a revision and remove it from the system or to view that particular version of the Asset. The version tag name is a link that will take you to the Manage Revisions in Tag screen.|, - lastUpdated => 0, + message => q|

    This screen displays a list of all committed versions for the current Asset, showing the date it was committed or opened, who owns the tag for that version, and the name of the version tag. Icons will allow you purge a revision and remove it from the system or to view that particular version of the Asset. The version tag name in the list is a link that will take you to the Manage Revisions in Tag screen.|, + lastUpdated => 1165449841, }, 'asset toolbar title' => { diff --git a/lib/WebGUI/i18n/English/Asset_Collaboration.pm b/lib/WebGUI/i18n/English/Asset_Collaboration.pm index 31bb080aa..328a1dd4a 100644 --- a/lib/WebGUI/i18n/English/Asset_Collaboration.pm +++ b/lib/WebGUI/i18n/English/Asset_Collaboration.pm @@ -1063,8 +1063,8 @@ properties listed below:

    }, 'display last reply description' => { - message => q|If set to Yes, template variables will be added to allow the display the last Post.|, - lastUpdated => 1163013333, + message => q|If set to Yes, template variables will be added to allow the display of the last reply in this Thread.|, + lastUpdated => 1165449294, }, 'system template description' => { @@ -1506,8 +1506,8 @@ the Collaboration Asset, the user will be notified.|, }, 'enable avatars description' => { - message => q|

    Select "Yes" to display Avatars for users in the Collaboration System. The Avatar field inthe User Profile has to be enabled, and users will need to upload an Avatar image to display.

    Using Avatars will slow down the performance of Collaboration Systems.

    |, - lastUpdated => 1131432717, + message => q|

    Select "Yes" to display Avatars for users in the Collaboration System. The Avatar field in the User Profile has to be enabled, and users will need to upload an Avatar image to display.

    Using Avatars will slow down the performance of Collaboration Systems.

    |, + lastUpdated => 1165449336, }, 'collaboration rss template title' => { diff --git a/lib/WebGUI/i18n/English/Commerce.pm b/lib/WebGUI/i18n/English/Commerce.pm index 438265aa6..f51be4255 100755 --- a/lib/WebGUI/i18n/English/Commerce.pm +++ b/lib/WebGUI/i18n/English/Commerce.pm @@ -134,7 +134,7 @@ our $I18N = { 'daily report email description' => { - message => q|

    Everyday the scheduler plugin that checks and updates subscriptions send a report on on the successful and failed term payments. Here you can set to which email address it should send this report.

    |, + message => q|

    Everyday the scheduler plugin that checks and updates subscriptions sends a report with the successful and failed term payments. Here you can set to which email address it should send this report.

    |, lastUpdated => 1138922899, }, @@ -396,8 +396,8 @@ our $I18N = { }, 'salesTaxRate' => { - message => q|The sales tax rate, as determined by the user's homeState in their profile.|, - lastUpdated => 1161319799, + message => q|The sales tax rate, as determined by the user's homeState in his/her profile.|, + lastUpdated => 1165449949, }, 'totalSalesTax' => { @@ -422,11 +422,11 @@ our $I18N = { 'help checkout confirm template body' => { - message => q|

    This template separates normal and recurring items. A normal item is an item that is payed only once. Recurring items are payed once a period, like a subscription.

    + message => q|

    This template separates normal and recurring items. A normal item is an item that is paid only once. Recurring items are paid once a period, like a subscription.

    The following template variables are available in this template:

    |, - lastUpdated => 1149221368, + lastUpdated => 1165449926, context => q|The body of the help page of the confirm checkout template.| }, diff --git a/lib/WebGUI/i18n/English/VersionTag.pm b/lib/WebGUI/i18n/English/VersionTag.pm index ca17745b4..73dbdb477 100644 --- a/lib/WebGUI/i18n/English/VersionTag.pm +++ b/lib/WebGUI/i18n/English/VersionTag.pm @@ -356,7 +356,7 @@ our $I18N = { }, 'commit version tag body' => { - message => q|

    Committing the version tag will make it the current version that is used and displayed on your website.

    + message => q|

    Committing the version tag will make its content the current version of content that is used and displayed on your website.

    |, lastUpdated => 1148444236, }, diff --git a/lib/WebGUI/i18n/English/Workflow_Activity_CacheEMSPrereqs.pm b/lib/WebGUI/i18n/English/Workflow_Activity_CacheEMSPrereqs.pm index a3a2d3b68..b6f6da554 100644 --- a/lib/WebGUI/i18n/English/Workflow_Activity_CacheEMSPrereqs.pm +++ b/lib/WebGUI/i18n/English/Workflow_Activity_CacheEMSPrereqs.pm @@ -8,8 +8,8 @@ our $I18N = { }, 'cache ems prereqs body' => { - message => q|

    This workflow activity caches all possible required events for an EMS. When the activity is triggered, it will take the first EMS that is found in the system and then process the events for preqrequisites. Since this process may take a very long time, it will process as many events as it can in one minute with a minimum of one complete event being processed. Then it will pause and reque itself so that other activities can be processed.

    |, - lastUpdated => 0, + message => q|

    This workflow activity caches all possible required events for an EMS. When the activity is triggered, it will take the first EMS that is found in the system and then process the events for prerequisites. Since this process may take a very long time, it will process as many events as it can in one minute with a minimum of one complete event being processed. Then it will pause and reque itself so that other activities can be processed.

    |, + lastUpdated => 1165449130, }, }; diff --git a/lib/WebGUI/i18n/English/Workflow_Activity_CommitVersionTag.pm b/lib/WebGUI/i18n/English/Workflow_Activity_CommitVersionTag.pm index 783a0bbec..af3efd64c 100644 --- a/lib/WebGUI/i18n/English/Workflow_Activity_CommitVersionTag.pm +++ b/lib/WebGUI/i18n/English/Workflow_Activity_CommitVersionTag.pm @@ -9,8 +9,8 @@ our $I18N = { }, 'commit version tag body' => { - message => q|

    This workflow activity commits a version tag. It should be used as the last step in any workflow dealing with committing version tags. For example, if you built a workflow that required someone else to authorize the committing of a version tag, this activity would be the last step in the workflow and its execution would depend on the authorization actually heppening and being positive.

    |, - lastUpdated => 0, + message => q|

    This workflow activity commits a version tag. It should be used as the last step in any workflow dealing with committing version tags. For example, if you built a workflow that required someone else to authorize the committing of a version tag, this activity would be the last step in the workflow and its execution would depend on the authorization actually happening and being positive.

    |, + lastUpdated => 1165449726, }, };