Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There is a problem when you want to install drupal with a different language than English. As you know, you should follow the link 'Learn how to install Drupal in other languages' shown in the first page during install. On the following page you find the instructions on how to accomplish this, which states:
If an alternative translation package of your choice is available, download and extract its contents to your Drupal root directory.
When in fact, drupal looks for the .po file inside profiles/$profilename/translations, not in root directory. So, returning to the first page never shows the new language.
Comment | File | Size | Author |
---|---|---|---|
#2 | hu-6.0-dev.tar_.gz | 181.52 KB | Gábor Hojtsy |
#1 | install-translation.patch | 562 bytes | robertgarrigos |
Comments
Comment #1
robertgarrigos CreditAttribution: robertgarrigos commentedI read that strings are frozen on RC so this can be solved by changing the scanned directory. This is a patch for this.
Comment #2
Gábor HojtsyNo no. The instructions say:
- grab a language *package*
- *extract* it to the Drupal root directory
Now here is a language package (the current Hungarian translation). Extract this to the Drupal root directory, and all files fall into the right place.
Comment #3
robertgarrigos CreditAttribution: robertgarrigos commentedOk, I see. This is right if you extract by command line but it's not if you do so with a GUI. This is, with my Mac, extracting by double clicking on the file it doesn't extract each file into its right place. I wonder if this is not confusing, in the first place, and if we are excluding from a proper instal.lation to the people that cannot expand a .gz file by the command line within their hosting package or doesn't have a hosting control panel that extracts a .gz file for them. Shouldn't we, at least, explain this a little bit more?
Comment #4
Gábor HojtsyWe are definitely not explaining this more on the Drupal 6 screen, which was already deemed too long for people to read and find comfortable. Actually the Mac is the only platform, which has these problems with rewriting stuff instead of merging on extraction and copy/move. (I also use a Mac, but I am not using the Finder for these kinds of stuff). Drupal 6 cannot include full stories for all systems. Depending on what software you use, you can achieve the same effect differently. This is where the drupal.org handbook can help, and I hope it will help. Only those who use these different software can document the different processes at the end. Feel free to repurpose this as a documentation task.
Comment #5
robertgarrigos CreditAttribution: robertgarrigos commentedI agree that the drupal handbook should be the place for looking for further information and I would put a link to it on that particular paragraph. I think the scope of this issue goes further away than a Mac users issue. I'm thinking of the people using an ftp client to upload an extracted drupal to their hosting and, most provably later, the extracted language files. So a link to the documentation page on the installation screen would be very handful for many users.
Comment #6
Gábor HojtsyI agree and would welcome a link there as soon as there is a documentation page to link to.
Comment #7
lauscherli CreditAttribution: lauscherli commentedi still struggle with this.... does this documentation-page exist? can't find it... this was much easier in drupal5!!!
Comment #8
Gábor Hojtsy1. Download langauge package.
2. Extract to Drupal's root directory, where Drupal is already exctracted.
3. Enjoy that all files fall into place, such as modules/system/translations/*.po.
If you don't see 3. working, then figure out what went wrong in 2.
Comment #9
Gábor HojtsyShould now be documented in the handbooks.
Comment #10
StefanScottAlexx CreditAttribution: StefanScottAlexx commentedThank you for this info Gabor, where you stated:
By the way, this also agrees with the info here: http://11heavens.com/building-powerful-and-robust-websites-with-drupal-6...
But I've tried this using Drupal 6.6, and I'm getting an error message.
Here's what I did:
1. First I made sure there are NO languages (other than English) currently installed, because the site:
http://11heavens.com/building-powerful-and-robust-websites-with-drupal-6...
says:
2a. I downloaded the language package (eg, Brazilian Portuguese):
http://ftp.drupal.org/files/projects/pt-br-6.x-1.0-rc5.tar.gz
from here:
http://drupal.org/project/translations
2b. Then I uploaded this to my public_html directory (which in my case is the same thing as my Drupal installation directory - because I'm using a free, shared web hosting provider which doesn't give me access to the file .htaccess which would be needed to redirect http://mydomain.com/mydrual to http://mydomain.com).
2c. Then I used cPanel File Manager to extract the compressed tarball (eg, pt-br-6.x-1.0-rc5.tar.gz) to the Drupal installation directory. (By the way, earlier I was doing this wrong - I was putting it into a subdirectory within the Drupal directory, eg ../public_html/pt-br/ or ../public_html/pt-br-6.x-1.0-rc5.tar - because I didn't realize that extracting the tarball would 'scatter' or 'slot' the files being extracted all into the proper subdirectories, due to the fact that the tarball directory structure is the same as the Drupal directory structure).
I then repeated the above steps for another language (eg, Spanish), so as to be able to test if the error message (shown below in the 'code' box) is reproducible for these two language packages (and it is - meaning that this is probably not a problem with the language packages themselves.
I believe that the .po files have been extracted to the proper locations. For example, if I use cPanel File Manager to go to this directory...
/public_html/modules/block/translations
...it contains the following two files...
modules-block.es.po
modules-block.pt-br.po
... for Portuguese (Brazilian) and Spanish, before I perform my step 3 below.
3. Then I went to:
http://mydomain.com/admin/settings/language/add
and added the language (eg, Portuguese (Brazilian)).
and I got the following error message:
After the error message is displayed, the language does appear in the list of installed languages here:
http://mydomain.com/admin/settings/language
And if I go here:
http://mydomain.com/admin/build/block
and add a 'Language Switcher' block to my page layout, it does show up with the right language.
And clicking on a non-default language in the Language Switcher on my home page does create the correct URL, eg:
http://mydomain.com/pt-br
http://mydomain.com/es
However, all pages are still displayed in English.
By the way, as an alternative I also tried going here:
http://mydomain.com/admin/settings/language/configure
before doing my step 3, and selecting either 'Path prefix only' or 'Path prefix with language fallback' (instead of the default selection 'None') to see if selecting either of these helped avoid the error message generated in my step 3 - but I still got the error message.
Any suggestions would be most welcome!
Comment #11
StefanScottAlexx CreditAttribution: StefanScottAlexx commentedBy the way, this page of my site:
http://mydomain.com/admin/build/translate
says this:
I am concerned that the percentages are both 0% here. Could this be the cause of the problem?
Comment #12
Gábor HojtsyIt will be more then 0% after the imports actually happened. I'd advise you to use "no language negotiation" first, to avoid having possible path routing problems. And then if the import still does not work for some reason, we can debug from there.
Comment #13
lauscherli CreditAttribution: lauscherli commentedAll the time I had problems with step nr. 2 on my mac......!!! I found a very helpful video-podcast on lullabot going about that: should help everybody solve the problem! http://www.lullabot.com/node/330/play (and who hasn't got stuffit, there's a free version for downloading).
Comment #14
lauscherli CreditAttribution: lauscherli commentedAll the time I had problems with step nr. 2 on my mac......!!! I found a very helpful video-podcast on lullabot going about that: should help everybody solve the problem! http://www.lullabot.com/node/330/play (and who hasn't got stuffit, there's a free version for downloading). SORRY FOR THIS UNINTENTIONAL DOUBLE-POST!
Comment #15
zzolo CreditAttribution: zzolo commentedIf Gábor has created a page (no link available above), then the rest of this ticket seems like it is more of a support issue than documentation? Confirmation?
Comment #16
robertgarrigos CreditAttribution: robertgarrigos commentedI think we could use this page to link to: http://drupal.org/node/21145
Comment #17
arianek CreditAttribution: arianek commentedagreed zzolo - this docs issue seems to have been dealt with - moving to translation issue queue as a support issue
Comment #18
Kars-T CreditAttribution: Kars-T commentedHi
I am closing this issue to clean up the issue queue. Feel free to reopen the issue if there is new information and the problem still resides. If not please make sure you close your issues that you don't need any more.
Maybe you can get support from the local user group. Please take a look at this list at groups.drupal.org.