Copied to clipboard

Flag this post as spam?

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


  • emaadali 55 posts 95 karma points
    Sep 30, 2014 @ 18:11
    emaadali
    0

    Infrastructure issue: document type does not exist, or it does not have the right alias or is not an allowed child nodetype

    Hi,

    I am using latest polyglot package. And having issues.

    Below showing structure of my doc type HomepageTranslationFolder is child of home. And HomepageTranslation is child of HomePageTranslationFolder

     

    Please tell me what messing in there.

     

  • dimi309 244 posts 578 karma points
    Oct 01, 2014 @ 06:52
    dimi309
    100

    Hi emaadali,

    Thank you for your interest in Polyglot! :)

    The "inherritance" relationships between the document types is not important. As a matter of fact, there is no point in making the translation folder the parent of the translation document type, because they do not share the same properties. Typically the translation folder document type is empty of properties. You can add some if you would like to, but they are not needed by the package. What is important, in order for you to have document types that will allow the package to work, are the following points:

    • For a document type which will be translatable, a translation folder document type must exist, and it must be allowed to be a child node of the translated document type in the Umbraco content tree. You can set this by selecting "structure" from the editing screen of the document type to be translated and then checking the translation folder as an allowed child node.
    • A translation document type must also exist, which is allowed to be a child of the translation folder document type in the Umbraco content tree (you can set this, again, via the structure tab mentioned above).
    • The translation document type must have a property of type "label", the alias of which must be "language".
    • The translation document type must have properties of the same type and alias as the document type which will be translated, but only for those properties which are going to be translated. For example if you have a property to which you are going to be uploading an image which will be the same across all languages, you do not need to provide a translation property for it.
    All of this is described in even greater detail in the documentation. A video tutorial is also available: http://www.dailymotion.com/video/x197yds_polyglot-package-for-umbraco-tutorial_tech (it is a little old and, in it, I use an older version of Umbraco, but the general idea has not changed much since I produced it).
    Please let me know if you need any more help.
  • emaadali 55 posts 95 karma points
    Oct 05, 2014 @ 10:57
    emaadali
    0

    Hi Dimtri,

    Thanks for your response. I have installed your latest release which is working as it wants to be :). Really love your product and I am using it from last 2 years in multiple websites. 

    One thing I need to say you is that it will be great if you add some documentation related to umbraco 7. I mean a new demo in which you explain how node transalation is done. At the moment I need to use @RenderPage("~/macroScripts/PropertyReferenceTranslation.cshtml", CurrentPage.Id, "bannerHeader", selectedLanguage) To get resultant information with appropriate culture.

    Don't asking for a very long document just 2,3 pages to explain how we get information using Model.Content or CurrentPage etc in templates and partial views.

    Keep it up and thanks your help :)

  • dimi309 244 posts 578 karma points
    Oct 05, 2014 @ 11:12
    dimi309
    0

    Hi emaadali,

    Many thanks for the kind feedback!

    Since you have mentioned PropertyReferenceTranslation, perhaps this support thread will interest you:

    https://github.com/dimitrikourk/Polyglot/issues/1

    The bottom line is, in the latest release, there is a macro that offers the PropertyReferenceTranslation functionality, thus simplifying things and sparing developers from even having to pass the language as a parameter. I have updated the Umbraco 7 package documentation accordingly.

    About using Model.Content and CurrentPage in templates, I am wondering if it is more of an Umbraco subject rather than a Polyglot specific subject. Please let me know if I have not understood the question. If something needs to be better explained in the Polyglot documentation, I will try to clarify it as well as possible.

    Cheers,

    Dimitri

Please Sign in or register to post replies

Write your reply to:

Draft