Item Languages
The section on working with items provided a variety of examples in retrieving items based on their language. In this section will show how to manage items and their languages.
Add Language Version
Example: The following example queries all of the content items and adds a new language version of "en-ca", while overwriting any that exist.
Example: The following example adds a language version from English to US and Polish while leaving the Title
field blank. If a version already exists nothing happens.
Example: The following example adds a language version from English to Polish of Template Name Sample Item. If the version exists a new version is created for that language. Finally the results are displayed as a table showing only the Name
, Language
, and Version
.
Example: The following example adds a language version in Polish to the Home item and all its children. If the version exists nothing happens. No fields were harmed in the making of this version.
Remove Language Version
Example: The following example queries all of the content items and removes the language version of "fr-CA".
New Item with Forced Language Version
Example: The following example creates a new item with language versions only matching the specified languages; all other language version are removed.
Parameters and Configuration
Supported parameters:
-Recurse
Translates item and its children-IfExist
Accepts one of 3 pretty self explanatory actions:Skip
,Append
orOverwriteLatest
-TargetLanguage
accepts a list of languages that should be created-DoNotCopyFields
creates a new version but does not copy field values from original language-IgnoredFields
list of fields that should not be copied over from original item this can contain e.g.__Security
if you don't want the new version to have the same restrictions as the original version.
On top of the ignored fields in the -IgnoredFields
the following fields are ignored as configured within the Spe.config
file:
References
Last updated