Modules are ordered by filename, and not the 'displayname' on admin/build/modules.

This is esp. obvious now that we have a Content Translation module.

Comments

heine’s picture

StatusFileSize
new984 bytes

And one for 5.x - just because of the different file.

robloach’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new903 bytes

I knew something didn't look right. When I applied your patch (dated from September), I got some offset hunks, so here's the updated patch. After applying, the modules appeared in the correct order.

gábor hojtsy’s picture

Status: Reviewed & tested by the community » Fixed

My first reaction was that we should sort with the localized module name, but then looked into the code and realized that we are not actually localizing the module names. I remember some discussions about keeping this for consistency and security reasons (so to know where to get that module, you need to know the exact name). Anyway, as we are not localizing the module names, this patch actually works as advertised, so committed, thanks.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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

heine’s picture

Version: 6.x-dev » 5.x-dev
Status: Closed (fixed) » Needs review

5.x has the same issue.

robloach’s picture

Status: Needs review » Reviewed & tested by the community

Patch applies cleanly and sorts as expected.

drumm’s picture

Status: Reviewed & tested by the community » Fixed

Committed to 5.x.

Anonymous’s picture

Status: Fixed » Closed (fixed)

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