Aimeos
Finally, we've applied your workaround because it's the best option so solve the problem. The changes are included in 22.10.1+
Yes, traits might be a good idea to spit the code into several files
Dividing the source code like that looks reasonable. Can you create a PR that splits the code like that?
The config view helper should return overwritten values by the site. Can you post a screenshot from the sites config table for that setting?
In theory it should work because the config from the site item is applied to the config object here: https://github.com/aimeos/aimeos-laravel/blob/master/src/Aimeos/Shop/Command/AbstractCommand.php#L65 Can you check if the key is available after that...
Can you check if `$config->get( 'controller/jobs/product/import/csv/location' )` in line 66 returns something?
Does `$siteItem->getConfig()` contains the configuration you want?
Then, you are using a different site which doesn't contain the mentioned configuration settings. You can specify the site for the job as last parameter: ``` php artisan aimeos:jobs product/import/csv...
This doesn't work in the admin backend yet because the site config isn't applied to the config item of the context here: https://github.com/aimeos/aimeos-laravel/blob/master/src/Aimeos/Shop/Controller/JqadmController.php#L257-L259 If you can create a PR, we...
We want to switch to Symfony 6 directly