I’ve installed Polyglot and I’m finding it
extremely useful when setting up a multi-lingual site. I think it’s brilliant!
My implementation (upon right-clicking and “[Create
translations]”) creates a translation folder that houses nodes used for the
actual translations.
However, even though “English (en)” is un-ticked
by default, I need it removing from the list as I have a parent node (above the
translation folder) that is to be the default node for English.
I’m concerned that a confused CMS user will
tick “English (en)” and a translated English page will appear - resulting in a default node (for English) and a translated node, also for English.
I was considering removing “English (United
States)” from the Languages folder in the Settings section in Umbraco as I’m
pretty sure it would drop out of the “Languages to be created” list if I did.
The only problem is, this feels like it could have major repercussions within
my Umbraco site, if I were to do this.
First of all, many thanks for your kind comments on this package. I greatly appreciate them!
The existence of the unchecked English option is actually a feature :) In the case when you would happen to have your text in a language other than your default one (English in your case), you could enter the text in that other language in the basic node and then create a translation in English later. It may sound a bit crazy to do this, but it is possible (please see page 4 of the documentation pdf for a detailed explanation of how the creation of translations works).
In any case, I would highly recommend not to remove the English language from your site. Polyglot considers the first language declared in Umbraco to be the default one, so it would consider French to be the default and it would just replace English as the unchecked option by French. I don't know if there would be any repercussions in Umbraco itself as well...
I am preparing a version of the package that will be able to function with Umbraco 6. It is not ready yet, since Umbraco 6 is still a release candidate and I think there are going to be some bug fixes in the next release which will be necessary for the package. In the meantime however, I can make a release which will allow you to hide the the default language from the translation creation window, by adding a special setting in your web.config file. Do you think that would work for you? I think i should be able to release it by Sunday.
That makes a lot of sense - it's a good job I didn't remove it then! Wow - that would be great if you could make a release to support that option in web.config. The pages in my site will always be in English so I'd like to configure the option so as not to confuse any would-be CMS users!
Yes, definitely. In general, the package has been tested and works with all 4.x versions from 4.5 onwards and its coming version will continue to do so. It still needs some adaptations for Umbraco 6. For those, I am waiting to see how the release candidate will evolve to adapt the package accordingly. But I will maintain backwards compatibility.
The new version of the package (v1.4), which allows for hiding the default language checkbox, has been released.
In order to upgrade, you just need to uninstall the previous version of the package and install this one. The created translations will not be deleted, since they are not part of the package. After the upgrade, all translation document types need to be configured to use the Translation template, as this setting will have been lost during the removal of the previous version.
Just add the following to your AppSettings, in web.config, in order to hide the default language:
I am getting an error of
"TranslationFolder document type GenericPage_TranslationFolder does not exist, or it does not have the right alias or is not an allowed child nodetype
"
My Polyglot Implementation
Hi,
I’ve installed Polyglot and I’m finding it extremely useful when setting up a multi-lingual site. I think it’s brilliant!
My implementation (upon right-clicking and “[Create translations]”) creates a translation folder that houses nodes used for the actual translations.
However, even though “English (en)” is un-ticked by default, I need it removing from the list as I have a parent node (above the translation folder) that is to be the default node for English.
I’m concerned that a confused CMS user will tick “English (en)” and a translated English page will appear - resulting in a default node (for English) and a translated node, also for English.
I was considering removing “English (United States)” from the Languages folder in the Settings section in Umbraco as I’m pretty sure it would drop out of the “Languages to be created” list if I did. The only problem is, this feels like it could have major repercussions within my Umbraco site, if I were to do this.
Does anyone have any ideas? Tips? Advice?
Many thanks in advance,
Rick
Hi Rick,
First of all, many thanks for your kind comments on this package. I greatly appreciate them!
The existence of the unchecked English option is actually a feature :) In the case when you would happen to have your text in a language other than your default one (English in your case), you could enter the text in that other language in the basic node and then create a translation in English later. It may sound a bit crazy to do this, but it is possible (please see page 4 of the documentation pdf for a detailed explanation of how the creation of translations works).
In any case, I would highly recommend not to remove the English language from your site. Polyglot considers the first language declared in Umbraco to be the default one, so it would consider French to be the default and it would just replace English as the unchecked option by French. I don't know if there would be any repercussions in Umbraco itself as well...
I am preparing a version of the package that will be able to function with Umbraco 6. It is not ready yet, since Umbraco 6 is still a release candidate and I think there are going to be some bug fixes in the next release which will be necessary for the package. In the meantime however, I can make a release which will allow you to hide the the default language from the translation creation window, by adding a special setting in your web.config file. Do you think that would work for you? I think i should be able to release it by Sunday.
Cheers,
Dimitri
Hi Dimitri,
Many thanks for your lightning quick response!
That makes a lot of sense - it's a good job I didn't remove it then!
Wow - that would be great if you could make a release to support that option in web.config. The pages in my site will always be in English so I'd like to configure the option so as not to confuse any would-be CMS users!
Many thanks,
Rick
Hi Rick,
You're welcome! We'll do that.
I'll let you know when it's ready.
Best regards,
Dimitri
Hi Dimitri,
One thing I forgot to ask you - will the package you are releasing be compatible with 4.11.0?
Many thanks,
Rick
Hi Rick,
Yes, definitely. In general, the package has been tested and works with all 4.x versions from 4.5 onwards and its coming version will continue to do so. It still needs some adaptations for Umbraco 6. For those, I am waiting to see how the release candidate will evolve to adapt the package accordingly. But I will maintain backwards compatibility.
Cheers,
Dimitri
Hello Rick,
The new version of the package (v1.4), which allows for hiding the default language checkbox, has been released.
In order to upgrade, you just need to uninstall the previous version of the package and install this one. The created translations will not be deleted, since they are not part of the package. After the upgrade, all translation document types need to be configured to use the Translation template, as this setting will have been lost during the removal of the previous version.
Just add the following to your AppSettings, in web.config, in order to hide the default language:
<add key="PolyglotHideDefaultLanguageCheckbox" value="true" />
Brilliant - thank you Dimitri.
Thank you for the speedy release!
Rick
No problem! Glad I could help!
Dimitri
I am getting an error of "TranslationFolder document type GenericPage_TranslationFolder does not exist, or it does not have the right alias or is not an allowed child nodetype "
is working on a reply...