Magento 2: no assets generated when using custom magento_themes without split_static_deployment

[enr-beck-mellow]

• Deployer version: 7.3.3
• Deployment OS: MacOS

When using a custom magento_themes configuration like
->set('magento_themes', [ 'myvendor/theme-at' => 'de_AT', 'myvendor/theme-be' => 'fr_BE nl_BE', ]);
and not setting "split_static_deployment" to true no assets are generated.

The problem is in

deployer/recipe/magento2.php

Lines 188 to 193 in ef0087d

	if (count(get('magento_themes')) > 0 ) {
	foreach (get('magento_themes') as $theme) {
	$themesToCompile .= ' -t ' . $theme;
	}
	}
	run("{{bin/php}} {{release_or_current_path}}/bin/magento setup:static-content:deploy --content-version={{content_version}} {{static_deploy_options}} {{static_content_locales}} $themesToCompile -j {{static_content_jobs}}");

where its only checked if there are multiple themes to process and then the language configurations from the custom configuration get passed as theme names.

[peterjaap]

Where do you get this notation from?

   ->set('magento_themes', [ 'myvendor/theme-at' => 'de_AT', 'myvendor/theme-be' => 'fr_BE nl_BE', ]);

I've never seen that before and it looks like we've just never supported it.

[enr-beck-mellow]

I found this in the documentation and in the magento2 recipe itself

deployer/recipe/magento2.php

Lines 37 to 41 in ef0087d

	// set('magento_themes', [
	// 'Magento/luma' => null, - Will compile all languages from {{static_content_locales}} for Magento/luma
	// 'Custom/theme' => 'en_US fr_FR' - Will compile only en_US and fr_FR for Custom/theme
	// 'Custom/another' => '{{static_content_locales}} it_IT' - Will compile all languages from {{static_content_locales}} + it_IT for Custom/another
	// ]); - Will compile this theme with every language

[peterjaap]

Ah, that was introduced through #3326 by @renttek. Julian could you take a look here?

[renttek]

I'll take a look into this

[akosglue]

I could reproduce this and I suggest the following change:

this foreach:

foreach (get('magento_themes') as $theme) {
    $themesToCompile .= ' -t ' . $theme;
}

should be changed to this:

$themes = array_is_list(get('magento_themes')) ? get('magento_themes') : array_keys(get('magento_themes'));
foreach ($themes as $theme) {
    $themesToCompile .= ' -t ' . $theme;
}

because it should obviously work for each of the following configurations:

//1.
set('magento_themes', []);

//2.
set('magento_themes', ['Magento/luma', 'Custom/another']);

//3.
set('magento_themes', [
    'Magento/blank'   => 'nl_BE',
    'Magento/luma'   => null,
    'myvendor/theme-at' => 'de_AT',
    'myvendor/theme-be' => 'fr_BE nl_BE',
    'Custom/another' => '{{static_content_locales}} it_IT',
]);

So either the array values are iterated or the keys of the associative array.
(when it is empty the foreach is not reached because of the count check)

wdyt?

[akosglue]

and to be consistent with the other 2 method calls of setup:static-content:deploy, the -f switch should be added as well.

[peterjaap]

@akosglue that looks like a very good solution 👍 Could you PR it up?

[akosglue]

So I opened that PR but it fails when checking the docs. I have updated it though but now I am not sure hot to proceed with the fix.
The changes are similar somehow, there it was ok, but in my PR it fails:
https://github.com/deployphp/deployer/pull/3812/files
https://github.com/deployphp/deployer/pull/3818/files

[peterjaap]

Merged by now