I have attached two screen shots - one before and after applying my patch. I think the images explain the problem better than words, but in case you wonder why I file it as a bug: If a module has a remote update for a language, it always says that there is local update available too - behind the module name. I also removed two CSS classes for the module name (when there is an update available) because I think the display was better - compare the images.

Patch attached.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sutharsan’s picture

I support with your intention to improve this interface page, I thought WTF when I first watched this page. Although I don't have an alternative yet, your solution is not correct. This double indication is only double if the site has only one language, but it may prove usefull when the site has multiple languages. Then it is the status summary of all translations of a single module.

I will contact Bojhan or others of the UX team to help to improve this interface.

hansfn’s picture

My solution isn't perfect, you mean ;-) Of course not, but it's an improvement. How many sites have multiple languages (different than English). Even with two languages I would say that the duplicate indication is just noise. If you have say 3-5 languages, then I can see the need for the status summary, but then I wonder what the summary should be if 2 of the languages have updates, and 3 not?

Anyway, the bug isn't about duplicate indication - the bug is that the status summary indication (for updates) is wrong.

Sutharsan’s picture

I have reworked the design of the Translate Interface Update page: #1029554: Translations update feature user experience In which I use a different approach to the summary status indication.

Sutharsan’s picture

Status: Active » Closed (duplicate)

I mark this issue as duplicate of #1029554: Translations update feature user experience. Please join our effort over there and review the new patch.