Unable to update images in design configuration form

[faisal2010]

Preconditions

1. Download & install a fresh copy of magento CE 2.3.0 without sample data either through composer or archive package from Magento download page.
2. Did not make any change in database and files.

Steps to reproduce

1. Login to admin
2. Click on Content form left menu and click Configuration under Design.
3. Click Edit in Action column on any of the three default record from grid.
4. Click on HTML HEAD tab under Other Configuration section.
5. Upload an image to Favicon Icon through upload button.

Expected result

1. Image should upload instantly through ajax and show a preview

Actual result

1. Page just flick sightly and nothing happens.
2. Click on Save and Continue or Save Configuration button. A success message display but image path is not saving in database nor image upload to disk.

Additional information

The image uploadeConfig defined in form ui_component is not working correctly. Ajax uploader request url should be theme/design_config_fileUploader/save BUT it is going to theme/design_config/edit .

[magento-engcom-team]

Hi @faisal2010. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team 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-engcom-team 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.

[ghost]

Hi @faisal2010 thank you for you report, this issue has already fixed in 2.3-develop branch and will be available on 2.3.1 release

[ghost]

@faisal2010 -> #18851