I've done quite a bit of searching for this issue and haven't found an answer, so bear with me if it's a stoopid question :-)
When I run Update, I have a certain number of modules that report "no information". Some of these modules have no localization projects (browsed projects on localize.drupal.org), so this would be expected. However, in some cases, there are active localization projects, so why am I getting this status for these ?
My site is localized to French, and the following modules are reporting "no information":
civicrm_theme 6.x-1.4
facebook_status 6.x-3.0-rc3
logintoboggan 6.x-1.9
The localization project versions seem to match exactly with those on my site when I export the files. Is there a release process I'm not aware of for these .po files?
Thanks!
Comments
Comment #1
gábor hojtsyHave you looked at the http://localize.drupal.org/download page to verify that localize.drupal.org does in fact have downloads for these versions? (It does take some time for new versions to have translation downloads on localize.drupal.org).
Comment #2
Skidz commentedYes. That's what I was saying. There are translation files there that I can import manually (the ones listed). They don't update automatically though.
Comment #3
maxiorelI have the same problem with l10n_update 7.x-1.0-beta2
Comment #4
sutharsan commented@Skidz, are these problems persistent? I have downloaded and enabled civicrm_theme 6.x-1.4 and facebook_status 6.x-3.0-rc3 for French and both get updated as expected.
@maxiorel, please supply more information. This does not help. Can you reproduce your situation, and how?
@all: Always try the latest dev-release before you report a problem.
Comment #5
Skidz commentedActually, all three of the modules I listed are now happily updating themselves. I don't know why they've started working of late...
I have other modules that give me the "no information available" message, but I haven't had time to investigate those.
Comment #6
sutharsan commentedIf you do find the time, (much appreciated) pls use the dev release instead of the 6.x-1.0-beta1 listed here.
Comment #7
sutharsan commentedNo activity, closing the issue. Fee free to re-open if the problem persists.