-
Bug
-
Resolution: Fixed
-
Critical
-
2.1.4
-
None
-
Windows 10
-
-
Empty show more show less
-
Yes
-
Basel 87
-
5
The procedure for enabling CTS in content apps is documented at https://documentation.magnolia-cms.com/display/DOCS/Content+Translation+Support+module#ContentTranslationSupportmodule-Enablingcontenttranslationincontentapps. It works until you download the file and get a PathNotFound exception.
My configuration files are attached to DOCU-737.
Tested on Magnolia 5.4.8 SNAPSHOT and CTS 2.1.4 SNAPSHOT
Findings from the assignee
It turns out that the main problem is not to have workspace passed from action to the command. Once this achieved the main problem is solved.
Moreover, we have another problem with M.5-5-3 version which the DefaultProperty is not present anymore and replaced with ObjectProperty thus, the check in the code against DefaultProperty was not triggered and therefore the command was not working out of the box only for >= 5.5.3 version. These quirks are fixed now with the related PR.
Documentation Update
Labels should be present, otherwise fields will not be exported.
Workspace and formPath has to be defined in info.magnolia.module.contenttranslationsupport.commands.TranslationFileDownloadCommand under contentTransporter.