I am developing an in-house course in maintaining Drupal, and would like to explain how to update languages. I finally managed to get the update working (from behind our proxy) using the latest dev version, however I would also like to be able to work with local files.
However, when I set the update to work with "Local files only" and I update the information, I get the reply "Failed to fetch information about available updates from the server". I am not sure if this is a bug or not.
Also, it is not at all clear to me where I should put the local files. I tried creating (and configuring) sites/all/translations as the home for the translation files, and then putting the Drupal French po file there, but this changed nothing.

Comments

sutharsan’s picture

Was the README.txt not clear about this? You should place the files in the directory that you configured at admin/config/regional/language/update.

martink’s picture

Category: support » bug

Yes, that was what I had understood so I am glad I was right.
However, I have changed this to a bug, because in fact it seems that in the latest dev version the possibility of using local files has been switched off.
Example: at admin/config/regional/language/update I have configured the system to "use local files only". However, when I add the Views and Chaos tools modules it goes straight out to the remote server, downloads and installs the language files. In fact it seems to ignore completely the "use local files only".
Then if I go to admin/config/regional/translate/update and click on "Refresh information", I get the error message: "Failed to fetch information about available updates from the server."

sutharsan’s picture

Title: Where do I put the local files? » "use local files only" seems to be ignored when modules are enabled

Changing title to match new observation.

sutharsan’s picture

Status: Active » Needs review
StatusFileSize
new2.62 KB

Attached patch should solve the issue. Please test.

sutharsan’s picture

Issue summary: View changes
Status: Needs review » Fixed

Patch committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.