In talking with Gabor, as part of the D8 multi-language initiative the install process will pull down the list of current translations via l10n_update (which will be included in core) and present it before profile selection.


So, we'll probably have to work around this, both on the site form, and during the installation of D8 itself.

Marking this as 'postponed' as it hasn't made it into core yet. Also, this should probably be filed against 7.x-2.x, but that doesn't appear available in the 'Version' dropdown.


Steven Jones’s picture

Version: 6.x-1.x-dev » 7.x-2.x-dev
Steven Jones’s picture

Version: 7.x-2.x-dev » 6.x-2.x-dev
ergonlogic’s picture

Version: 6.x-2.x-dev » 7.x-3.x-dev
Issue summary: View changes

New features need to be implemented in Aegir 3.x, then we can consider back-porting to Aegir 2.x.

Grimreaper’s picture

Status: Postponed » Active


Switching the status to active as Drupal 8 is out now.

Grimreaper’s picture


Here are two patches to add this features.

One is for provision, the other one for hosting.

Thanks for the review.

ergonlogic’s picture

Status: Needs review » Needs work

Thanks for the patches.

It seems like the inline language list may result in us chasing a moving target. Is there any way to pull that data from, for example?

Grimreaper’s picture


Yes, having the available languages hardcoded is maybe not the best as it will need some updates time to time.

But that's how it works in Drupal 8 core and I searched for related issues and found this (old) ones:
- #568986-28: Dynamically update standard language list from localization server
- #2063055: Sync language list with translations (add fy, ga, hy, km, ms and sw)
- #912218: Add missing languages present on
- #568984: Define language list export format, set it up on ldo

I think it is made like this in core to avoid problems when in off-line mode and also because API on ldo is not ready (I can't find the API).