I have this information message when i click on refresh information.
I can say that the server is behind a proxy. My first idea is the problem become from that. But after verification the module use drupal_http_request, and i can run cron manually. So i think that i can trace the functions If you guide me a few.
Another information : I have no messages in watchdog.
| Comment | File | Size | Author |
|---|---|---|---|
| #17 | l10n_update-allow-alternate-http-client-750000-17.patch | 0 bytes | sutharsan |
| #15 | l10n_update-allow-alternate-http-client-750000-15.patch | 763 bytes | cyberwolf |
| #1 | l10n_update-proxy.patch | 2.54 KB | japerry |
Comments
Comment #1
japerryThe proxyhack fixes to drupal_http_request has to be applied to the l10n_update module:
http://drupal.org/node/7881
I'd suggest adding this following patch to the module, as it just adds some logic around variable_get functions, so even if you don't have the proxy hack installed, the module won't break.
Comment #2
ndm commentedWorks fine very thanks
Comment #3
ndm commentedComment #4
sutharsan commentedUpdating title to reflect the cause of the problem.
Comment #5
jose reyero commentedWell, I don't think this is really 'our problem'.
I mean, if you are behind such a proxy, all http requests will fail (Drupal core update, etc...) so we need a more global solution for that, like a core patch or a contrib module that deals with it.
We cannot fix this issue for every module that does an http connection.
Comment #6
pieterdcI agree with Jose; this solution isn't ideal.
But it works, for now.
Is a better solution possible while we're dealing with #527484: drupal_http_request can't be used in install profiles ?
Comment #7
soulfroysTanks @japerry!!!
I applied the two patches and finally getting to update Drupal core, modules, themes and translations... it's a miracle... :-)
Comment #8
lpalgarvio commentedHello
From what i'm testing, support for proxy in l10n_update in 7.x-2.0/2.x doesn't seem to be working.
It always reports "Missing translations for XXX projects".
I'm following the steps described in:
https://www.devincarlson.ca/blog/configuring-drupal-use-proxy-server-whe...
Using module http proxy + conf in settings.php
https://www.drupal.org/project/http_proxy
The Core mode update works fine. Can get update list for modules/core.
Comment #9
lpalgarvio commentedThe same happens for every language. And no matter how much testing we do. Update status is working fine.
Example:
Comment #10
martin.knapp commentedThis stopped working for me recently, and I cannot work out why. I'm running drush 8.0.2 and Drupal 7.41 with the http_proxy module configured (I have to say I'm running under Ubuntu 14.04 server installed on a VirtualBox VM). Everything else works: Drupal update status report, drush pm-update and module download, all fine. But when I run drush l10-update-refresh here is what I get:
Comment #11
martin.knapp commentedI've put a more detailed query on stackexchange - it would be really appreciated if somebody could look at this.
Comment #12
razunter commentedI think this issue can be caused by lack of SSL-related settings in php.ini (curl.cainfo)
Comment #13
nothinghere commentedSame problem for me : authenticated proxy didn't work for l10n_update module.
Behind my proxy, update drupal modules work fine since I've installed "cURL HTTP Request (chr)" module and "HTTP proxy (http_proxy)" module. But it seem l10n_update doesn't use it...
Please, help !
Comment #14
cyberwolf commentedI think this only changed quite recently, but all translation URLs are redirecting to their https version.
The problem with https, is that Drupal core's proxy code in drupal_http_request() also doesn't support proxying secured http connections (#924498: Proxy https support for drupal_http_request()). Since the code in l10n_update is basically a copy of that code, without the variable_set() and without the override feature (introduced in #1664784: drupal_http_request() has problems, so allow it to be overridden), it will also not support proxying secured http connections.
On our project we are using the chr module to 'override' the drupal_http_request() implementation and get proper proxy support. I believe adding the same override feature of drupal_http_request() to l10n_update_http_request(), and adding the chr module to your instance, would be the easiest way to fix the problem.
I'll be working on a patch for this during the week, will keep you informed.
Comment #15
cyberwolf commentedPatch attached.
Use it together with the chr module. Make sure you configure it correctly. You can enable the http client override via its UI, with Drush vset or in settings.php:
Comment #16
cyberwolf commentedComment #17
sutharsan commentedThanks, for sharing this. It is always better to re-use an existing solution.
Added some documentation to the patch.
Comment #18
sutharsan commentedComment #20
sir_gon commented#15 works like a charm!
Comment #21
sutharsan commented@sir_gon, Thanks for sharing.