Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Jonathan Richards 288 posts 1742 karma points MVP
    Jul 08, 2019 @ 17:32
    Jonathan Richards

    Error in Umbraco 7.13.2 and Translation Manager 2.3

    Hi Kevin,

    OK, I was having an issue with Translation Manager v2.3 with Umbraco 7.13.2 with my existing project

    But as it seemed to be failing immediately and also to make this bug report really simple. I've actually started with a brand new installation of Umbraco + Translation Manager, I've added nothing that I've not listed. I've created 2 doctypes and used 1 property.

    1. Create empty VS solution in Visual Studio 2017 version 15.9.16
    2. Create empty ASP.NET Web Application (.NET Framework) using .NET Framework 4.7.2
    3. Installed, using NuGet, Umbraco CMS version 7.13.2, use SqlServerCE, with no Starter Kit
    4. Install Translation Manager version 2.3
    5. I created a Site doctype that is allowed to be placed in the content Root
    6. I created a Text doctype, with only the Richtext editor (This is the one that comes as default with Umbraco, I haven't changed or amended this property editor at all). I allowed this Text Doctype to be a child of Site doctype Screenshot of Doctypes

    7. Next I create and publish a USA content node in the root of the content tree.

    8. Within the USA site, I created and published one child content node. I filled the only property editor that exists with some dummy text. Screenshot of USA content

    9. I then created and published a Denmark Content node in the root using the site DocType

    10. I added the Danish language to the Umbraco Instance, along with the default EN-US Screenshot showing the 2 languages installed into Umbraco
    11. Next I set the Culture and Hostnames of USA site to EN-US, and DA-DK for the Denmark site Screenshot showing Culture and Hostnames of Site node called Denmark
    12. In Translation Settings, created Translation set called Standard with Master set to USA site node and Sites containing Denmark site node. Nothing else was altered in the translation set. Screenshot showing Translation Set
    13. USA site is then Send to translation, I select Danish and include all children (There is only 1 child present, it is published) Screenshot showing USA being sent to translation
    14. In Pending of Translation Manager, I create a Translation Job by selecting All content and selecting XLIFF File as the Provider (I have tried the Translator Dashboard and receive same bug). I complete the task by pressing Submit Translation Job

    Screenshot of Translation Job 15. Under Submitted, I selected the file that was created in the previous stepScreenshot prior to pressing Upload File 16. I then click Upload file and I always receive an error that points to the first property. Screenshot showing error that I always receive

    Below is the xlf file, which I never amend or edit in anyway This is the xlf file, which I never amend or change in anyway

    This issue has appeared in a pre existing site that I have updated to Umbraco 7.13.2 and Translation Manager 2.3, I've only replicated this issue on a new clean site to show its not something specific to my real site. I'm happy to share the above Umbraco instance with yourself, but honest it contains nothing more than I've listed above.


    Jonathan Richards

  • Kevin Jump 1896 posts 11907 karma points MVP 4x c-trib
    Jul 08, 2019 @ 17:58
    Kevin Jump

    Hi Jonathan

    I'll take a look, but real quick - what happens if you copy the source value in the xliff to a taregt one ?


       <source>This is some text</source>
       <target>This is some text translated</target>

    when a translator translated the files with their software this is what it does (and its the error in the last screenshot).

    but I will just replicate your setup to see if i can see anything else

  • Jonathan Richards 288 posts 1742 karma points MVP
    Jul 08, 2019 @ 21:35
    Jonathan Richards

    Hi Kevin,

    I was unaware I needed the file to be amended, that does make the issue go away.

    Thanks for your help


    Jonathan Richards

Please Sign in or register to post replies

Write your reply to: