Magento 2.3.1
Set default setting in env.php, something like.
'system' => [
'default' => [
'dev' => [
'js' => [
'session_storage_key' => 'collected_errors'
],
'debug' => [
'debug_logging' => '0'
]
],
When env.php file is set with some values run bin/magento app:config:import
Processing configurations data from configuration file...
System config was processed
Process finished with exit code 0
The change in app/code/Magento/Store/etc/config.xml
Will resolve in an error Notice: Array to string conversion in https://github.com/magento/magento2/blob/21b3cafa7e2c2acea150d6555f23906e2872db61/lib/internal/Magento/Framework/App/Config/Value.php#L96 when running bin/magento app:config:import in relation to default values set in the env.php
By adding
Hi @govereem. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.3-develop instance - upcoming 2.3.x release
For more details, please, review the Magento Contributor Assistant documentation.
@govereem do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
i am working on it
It's not reproduced in Magento2.3.1
Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.3-develop branchDetails
- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
[ ] 5. Verify that the issue is reproducible on 2.2-develop branch. Details
- Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x
[ ] 6. Add label Issue: Confirmed once verification is complete.
[ ] 7. Make sure that automatic system confirms that report has been added to the backlog.
@magento give me 2.3-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento 2.3-develop instance for you
Hi @engcom-Bravo, here is your Magento instance.
Admin access: https://i-23442-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.
Hi @govereem thank you for your report. Please, rewrite your code on this:
'system' => [
'default' => [
'dev' => [
'js' => [
'session_storage_key' => 'collected_errors'
],
'debug' => [
'debug_logging' => '0'
]
]
]
],
Hi @govereem,
Had the same problem. I solved this by removing 'system_config_snapshot' inside the 'flag' table.
DELETE FROM flag WHERE flag_code = 'system_config_snapshot';
Thanks @davekleijnkega - it worked fine for me.
Can you please confirm it will not cause any affect for other configurations?
Thanks, @davekleijnkega - Even it worked for me too in the 2.3.5-p2 upgrade process.
Most helpful comment
Hi @govereem,
Had the same problem. I solved this by removing 'system_config_snapshot' inside the 'flag' table.
DELETE FROM flag WHERE flag_code = 'system_config_snapshot';