I'm really stumped here.
I've created a page with 3 languages, but the language switcher will not work properly.
I have translated both the menu entries and the content, and I want to use the language switcher to change both the menu item language and the content language.
What is happening now:
The language switcher points the browser to the node with the content translated, but the menu items are not working.
Or more exactly, the are for english, not russian.
I have in total 3 languages: Latvian, Russian and English, with Latvian as default. When I create some content in Latvian and the corresponding menu items, all is well. When I translate it into English, and add the menu items for English, all is well too, but the prefix for the link is not added. Since I'm using PathAuto, I believed, that that the language switcher would be using the newly generated node alias, but it is not. It is simply pointing to the node in English. But that is not the worst part.
When I select Russian, the content is translated, but none of the menu items appear. Also, sometimes, the prefix is added for russian, and then I can't revert back to Latvian, since there are no prefixes added for the default language, and the node alias is not displayed, only the node ID.
Any Ideas of how could I fix this? It is the only thing standing between me and completion of a project.
P.S. It almost seems, that Drupal was not made for this kind of a thing.
P.P.S I solved the problem for 2 languages - renamed English to Russian, since the client doesn't need English right now. I know, short term fix, but otherwise, my whole work would be in ruins.
Just in case someone else has a similar problem.
I fixed the language switcher issue by adding a path prefix for english.
My site's default language is spanish and I have english as a second one. I Installed everything, add the english prefix and followed the instructions of this site: http://openflows.com/blog/mvc/2008/10/03/drupal-6-i18n-basics
the prefix issue is discussed here: http://drupal.org/node/354069
Hope this helps
You can easily add the prefix for your languages by going to /admin/settings/language/edit/en
I had the same problem and this saved me the hassle of going and fixing it from the template.
The problem was in the template I was using. It rewrote all of the url's for beauty purposes, but didn't add prefixes correctly.
Related
I have three languages on my website English, French and Spanish. Either the translation is disabled in the paragraphs, then all languages are displayed as English (is also correct for me in some cases) or I enable the checkmark: "User may translate this field" in my paragraphs. But then I always have to adjust all three language contents.
Is there also a possibility, that it copies with the checkmark activated equal the English first of all as contents into all three languages and I then adapt the languages, which I can adapt also really as language.
At the moment, I then always pfege all three languages. In the worst case then three times the same content in English. This makes it of course very cumbersome?
Does anyone of you know the problem and is there a solution for it. Have I overlooked something in the configuration of my paragraphs.
I am using the latest Drupal 9 and the latest version of Paragraphs.
Thanks a lot
Bavra
I'm trying to figure out if there is a way how to set up Polylang (or some other translation plugin for WordPress) so that when I write an article or a page in one language (the default one) it will just make an exact copy of it and set it for the other languages. So the article/page is at least visible until I get my translator guy to translate it. Also he doesn't have to copy or write the article again and he just translates which is much more convenient.
Also, I'm struggling a bit with the translation of media. I know that I can turn it off, but I it would be awesome if I could use the same image and just add different translations to it, instead of uploading the same image for each language and just changing the description.
Thank you for your time :)
I'm trying to make a multilingual website in Drupal. My languages that I need are german, dutch, english and french. I've added the i18n module and added the languages.
I work with views to show my content on the website. For the moment I have one page that I want to translate in the 4 languages. I've created a view for each translation. Now I want to link my view to the correct node. Therefore I use a view field in my content node.
PROBLEM:
My problem lies in the url. The first time everything is fine.
my url: localhost/?q=nl/activiteiten
Now when I select english in my language bar the language changes but not the url. my url: localhost/?q=en/activiteiten
Here "activiteiten" must be "activities". How do I solve this?
I've searched a while for this problem on the drupal forums but I can't seem to find a good solution to this problem. The only thing I've found is working with a view field in the content node or with input_views in the body of your node. These two won't work for me.
i18 module with no need to create a view for each
language, you have to translate content using the i18, then
charge between changing the language.
You can have problems from the beginning did not use the module
all languages declared, you have to edit each
content and save it to associate it well.
Well, just reading your own answer I think you've taken a wrong turn somewhere (or you're trying to do something else and I didn't quite catch on).
To create multilingual views for pages (which is what I think you want to do) you would first create a page view (duh), specify what you want to be shown and define a path to it. Then you enable (if it's not enabled already) the URL-alias ("URL-aliassen") module and define aliases for each language (ie. FR : activites - I don't like accents in URLs :p - NL : activiteiten, DE : aktivitaten - if memory serves me right anyway, again with accents removed :p). These aliases will be used as the path from that moment on.
For an article describing this process refer to : Translating Views paths in Drupal.
BTW You could also use the Pathauto module to create these aliases based on the title of your nodes of course instead of defining them manually, you can even (re)create them in batch when you alter the settings.
Eventually I've solved my problem with a view field. I've made my view and in my node I've selected that view in the list. Then in the body you can type something for that language.
We have a Plone site that is primarily in English but has some content translated to French, and to a smaller degree had some pages originally in French and translated to English. In Plone 3, this has been working fine.
In Plone 4, a user whose language is set to "fr" can see virtually nothing - only those pages with a translation to French.
If we run ##language-setup-folders it gets worse - now anything that is defined as "language neutral" is invisible to English users too.
Surely, the intended behaviour is that a user whose language is set to English will see folders in "/Plone/en/...", and a French user will see "/Plone/fr/...", but if the page is not found it should fall back to /Plone. This is not happening.
Should it?
If so, under what conditions?
The language-neutral thing is a known bug, I believe. As to the fallback: as I understand it, the current behaviour is as follows: if you switch from en to fr and the current object does not have a fr translation the user is returned upwards towards the site root until there is a fr folder. (Or the root is reached.) No, I don't think that makes too much sense either, but at least a fr user will never see an en page. ;)
If you run ##language-setup-folders, you intitiate a setup that assumes that all content lives in the content-specific trees. The language folders are marked as INavigationRoot and will have the navtree and all anchored to the language folder.
You should basically assume each language to act as its own site with its own root.
— Except that translation management will keep "links" between translated versions of content and folders.
LinuaPlone only supports "full translations", that is, for every article there must be a translation. Very bad for many use cases where you only have one main language and only a subset of all articles actually needs to be translated... :(
You should have a look at http://plone.org/products/raptus.multilanguageplone (and its dependency http://plone.org/products/raptus.multilanguagefields). These addons do what you want :)
You can still make items language neutral. And this way they can still appear in the site of the other language via a collection.
I think setting items to Language Neutral used to work via "manage translations", but now it still works via:
Edit > Categorization > language
Select language neutral
I am working on a bilingual site in the latest version of Drupal 6. I installed the Internationalization module and the Views translation module, among many others.
The problem: On /admin/build/translate/search, some elements (e.g. the view title) appear in the text group "Views" and Drupal assumes they are in German, requiring an English translation.
Other elements (e.g. exposed filter labels) appear in the text group "Built-in Interface" and Drupal assumes they are in English, requiring a German translation. But in fact all the strings are in German:
To be clear, I am not seeing an issue with the language selection or the display of the view. The issue is when the page is first parsed by the language system and any translatable strings are inserted into the translation table. Drupal assignes different source languages for elements on the same page. The result is a mix of languages, once these strings are translated.
I thought that maybe it is the language preference of the user who hits the page first that interferes with this, but once I started changing it, I ran into this issue (reading the thread was eye-opening - it should be mandatory reading for anyone considering Drupal for enterprise-class solutions). Ok, now I have the URL prefix in the mix, which means that when a user changes the language preference, the site language does not change until they manually change the URL.
Once I managed to get the page rendered in English, it turned out that Drupal does not pick up the translation strings when the display language equals the source language. So no luck there.
I am ready to code my view in 2 languages, depending on what Drupal thinks the source language is for the various elements, but even that won't work. Has anybody else experienced this?
I think that you probably had basic mistake in how Drupal multilingual system work. I did the same mistake in the first multilingual Drupal site that I've built.
The most important thing to do is - if one of your languages is English - Use English in your code. if you need to put the word 'room' in one of the template use t('room') and not t('zimmer'). Your view titles? use English. Tag names and description? use English. The primary language should be English. After you setup your English site, you can translate your site using translate interface. I know it sound strange to one that his mother tongue is other than English, but I made several multilangual sites with i18n and it is the right way to do it with minimal complications.
Changing the admin interface language only change the interface - not the value. If you change the interface to German (i.e yoursite.com/de/admin/views) it doesn't mean that you are on 'German views'. It is the same view.
There are some exceptions - Multilingual variable as I explained here: How can I set a different homepage per language in Drupal?
I hope that is helpful.