Release Notes - FirstSpirit Data Provider

Java

17

250525

Update non-translatable language dependent target entity fields with source language content if empty.

250523

You can exclude translation of page or section form by setting adding a language dependent CMS_INPUT_TOGGLE component with the name st_translationstudio_locktranslation or pt_translationstudio_locktranslation-

250520

Lookup section with uid containing blank spaces.

241022

New event com.idmedia.translationstudio.firstspirit.export.IgnorePageFieldsIfTranslationExistsEvent added.

241004

Add target language to import operation commnt.

240718

You can exclude a page folder from being translated by setting its meta data toogle field mt_ts_donottranslate_folder to true.

240618

Hide all pure variable fields of Webforms instead of within element nodes only.

240516

Fix an issue in which link templates cannot be converted inside a DOM element.

240418.1

Fix GCA Page translation issue (HELPDESK #139406).

231219

Navigation folder not updated completely.

231102

If cloning entities, FS_CATALOG elements are checked to guarantee language consistencies.

230927

Webforms containing HTML code is imported correctly.

230714

Revisions created by the import operation will have a revision comment for easier identification later

Additional logging during the export operation can be activated by adding com.idmedia.translationstudio.firstspirit.operations.ExportFirstSpiritOperationProcess.level=FINE to your ./conf/logging.properties

Additional logging during the import operation can be activated by adding com.idmedia.translationstudio.firstspirit.importer.ImportUpdatedFilesIntoFirstSpiritOperation.level=FINE to your ./conf/logging.properties

230629

Improve reliability of method of identifying section folders.

230627

Custom messages fix.

230615

Fix a potential speed race causing file name collisions when splitting a translatable dataset xml into separate files.

230503

Correctly restore CMS_LINK in nested b nodes.

230424

Ignore variable-only and numeric-only webforms text fields when creating translatable xmls.

230420

Import of navigation caused all child folders to appear edited and requiring new release.

230413

CMS_INPUT_SECTIONLIST input component is fully supported.

230411

Monday Webforms are processed correctly in entities.

230214

Dataset template snippet settings are used to get entity display names.

221228

If a language dependent FS_CATALOG entitiy does not contain the expected target language, the field will still be processed because it might have been added later (HELP #76701).

220810

CMS_LINK in a table will be replaced as if inside a DOM node.

220802

Included page/section template name in translatable xml file.

220719

Fixed issue with updating import sync structural files and potentially failed lookups.

220127

Update to new TranslationStudio API version.

211215

Entities might not have been imported completely if FS_CATALOG column is of type NULL_COLUMN (HELP-55829).

211117

Trigger event IOnReceivedXmlFromCMSEvent if available.

211105

Failed imports may be retried if eligible instead of being moved into the error directory.

210903

Merging of language independent CMS_INPUT_LINK within language independent FS_CATALOG will be merged correctly, if it has language dependent content in it.

210806

Merging of language independent FS_CATALOG entity columns might have failed under specific circumstances.

210803

Fix an issue in which an empty language dependent catalog would not be overwritten with translated content, causing the import process to abort.

210723

Corretly process language independent FS_CATALOG cards with language dependent content deeper than 2 cards down (HELP-52362).

210520

Potentielle, unerwartete NullPointerException berücksichtigt (TSCORE-795).

210507

Bei fehlerhaftem FS-Access JAR kann ein NoClassDefFoundError auftreten und zu einer Endlosschleife führen. In diesem Fall ist ein Neustart unausweichlich und die Applikation wird vorsichtshalber gestoppt (TSCORE-794).

Sprachunabhängige FS_CATALOG Komponenten könnten inkorrekt als übersetzbar identifiziert werden, obwohl dies nicht stimmt (TSCORE-793).

Clarified XML processing logging.

210415

Language independent links with language independent FS_CATALOG will be added to the XML if they contian translatable texts.

Remove custom attribute from CMS_VALUE node

210408

Workflows to be executed on datasets after import are found correctly.

Links with identical label and url field (link properties configuration) will be processed as well.

210406

Import does not abort if trying to import empty catalog fields

210308.1

Domtable inside language independent catalog will be processed correctly.

210224

Translation flags now set prior import instead of later to avoid unnecessary FS API access.

Google Guava library version conflict between Google translate library and FS-Access library eliminated.

210224

Translation flags now updated during the generic update process instead of at a later stage to improve performance and reduce resource costs.

210211

Support for event to group xmls by translation request

Fixed counting when restoring links

Update of translated navigation fixed.

210203

Cloud user email addresses will be found

210112

XMLs will not be imported completely, if at least one paragraph does not contain any translated content.

Fixed synchronised XML lookup

201210

Page data will appear before the section paragraph nodes in the translatable XML file.

Link Elements inside a CMS_INPUT_DOM component will be parsed and (if configured properly in the link templates) only the link label remains inside the text node. All other text content is moved into a separate link group at the end of the XML document.

Fixed issue which tried to add the navigation references to fragments instead of non-fragment pages.

Datasets containing FS_CATALOG and only language independent fields will be identified correctly.

Looking up exported page reference files failed to find files where the structure’s folder equaled the pageref’s name.

Potential false positive duplicate sections identification fixed.

201012

Translatable id for custom messages fixed.

200909

Translatable XML files will be created in the temporary export directory and only moved to the translatable directory once processed completely.

FragmentCreator support