dev/js/minify_exclude returns array of results instead of string

[usman786cs]

Preconditions (*)

1. You should have installed Magento 2.3.4 version.
2. php version 7.2.

Steps to reproduce (*)

1. Add minification settings in config.php file
2. Run bin/magento app:config:import

Expected result (*)

1. Processing configurations data from configuration file...
2. Configuration processed

Actual result (*)

1. Import failed: Notice: Array to string conversion in vendor/magento/framework/App/Config/Value.php on line 100

I'm working on Magento version 2.3.4.
It was required by client to add minification settings in config.php file.
After I added them in config.php file . Below are the settings that I added:
'system' => [
'stores' => [
'default' => [
'dev' => [
'css' => [
'minify_files' => '1',
'merge_css_files' => '1'
],
'js' => [
'merge_files' => '1',
'minify_files' => '1',
'enable_js_bundling' => '0'
],
'template' => [
'minify_html' => '1'
]
]
]
]
]

After I run bin/magento app:config:import I get below error:
**Import failed: Notice: Array to string conversion in vendor/magento/framework/App/Config/Value.php on line 100
**

I was assuming that it will process configuration but useless.
After digging into it I found that vendor/magento/framework/App/Config/Value.php::getOldValue() returns array instead of string value against path dev/js/minify_exclude
Below is screenshot that shows result array contains array of three values instead of one string.
Can someone tell me how can i get rid of this issue.

Thanks!

[m2-assistant]

Hi @usman786cs. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@usman786cs do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[usman786cs]

I tried one solution which is
delete flag_data FROM flag WHERE flag_code = 'system_config_snapshot';

and it worked fine for me.

But is it fine solution or if it has disadvantages, please guide.

[m2-assistant]

Hi @engcom-Alfa. 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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Alfa]

Hi @usman786cs

Unfortunately, we are not able to reproduce the issue on a clean 2.4-develop.

Manual testing scenario:

1. Add minification settings in config.php file (devdocs) :
   

2. Run in console: bin/magento app:config:import

Actual Result:

✔️ Processing configurations data from configuration file...

✔️ Configuration processed

So, we have to close it.

Please, feel free to comment, reopen, or create new ticket according to the Issue reporting guidelines if you are still facing this issue on the latest 2.4-develop brunch. Thank you for collaboration.

[usman786cs]

Thanks @engcom-Alfa for your help.

I resolved this issue by this command:
delete flag_data FROM flag WHERE flag_code = 'system_config_snapshot';

But my question is, is it valid approach??

Thanks again

[hostep]

Hi @usman786cs: have you upgraded from Magento 2.2 to 2.3?
The structure of how the minify_exclude configuration has been defined changed in Magento 2.3.0 by #13687

I posed the question in the PR if there was a possibility that the configuration was stored in the database and how to handle that, but got no answer. So I think we needed to have some database upgrade script changing old structures to new structures in the database, but that didn't happen.

Other than that, I don't know what the system_config_snapshot flag is being used for or how the minify_exclude value got stored in there.
So if you could figure out what that flag does and what it is used for you can probably determine if it is important or not to keep or if it's safe to remove.

Sorry, this comment probably doesn't help you further I'm afraid.