Running magento 2.3.0 on php 7.1

I'm trying to upload an image for

Content > Design: Configuration > Transactional emails > Logo Image

And get the following error.

A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.

I've used this fix for the header and favicon image upload and it works but not for the above mentioned issue.

3 Answers 3


This is caused by a bug in magento 2.3.0, which will be fixed in 2.3.1 release. You obviously cannot wait until then and you definitely don't want to edit core files.

ref: https://github.com/magento/magento2/issues/18688

If you use composer to install/update magento 2.3.0 (if you don't, you should), you can apply a patch to the code via composer.

The process is explained here:


For completeness, here is the patch that is needed (edited as noted in the before mentioned link)

diff --git a/view/adminhtml/ui_component/design_config_form.xml b/view/adminhtml/ui_component/design_config_form.xml
index 8d4580f90c7b..bc1f36222dd6 100644
--- a/view/adminhtml/ui_component/design_config_form.xml
+++ b/view/adminhtml/ui_component/design_config_form.xml
@@ -54,7 +54,7 @@
                 <label translate="true">HTML Head</label>
-            <field name="head_shortcut_icon" formElement="fileUploader">
+            <field name="head_shortcut_icon" formElement="imageUploader">
                     <notice translate="true">Not all browsers support all these formats!</notice>
                     <label translate="true">Favicon Icon</label>
@@ -151,7 +151,7 @@
                 <label translate="true">Header</label>
-            <field name="header_logo_src" formElement="fileUploader">
+            <field name="header_logo_src" formElement="imageUploader">
                     <label translate="true">Logo Image</label>

You want to place this in a folder <magento root>/patches/composer (I named it : image-upload.diff)

and then adjust coposer.json accordingly

"extra": {
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/module-theme": {
                "MAGETWO-18688: Header logo image upload fix": "patches/composer/image-upload.diff"

The will ensure that the fix is not wiped when you deploy/update etc

  • Can you, who downvoted, please explain your reasoning.
    – ProxiBlue
    Commented Jan 11, 2019 at 0:55
  • 2
    This will work for store header and favicon icon, not for the transactional email logo. Commented Mar 25, 2019 at 10:21

This is the fix for this issue


       <label translate="true">Transactional Emails</label>
 -     <field name="email_logo" formElement="fileUploader">
 +     <field name="email_logo" formElement="imageUploader">
       <notice translate="true">To optimize logo for high-resolution displays, upload an image that is 3x normal size and then specify 1x dimensions in the width/height fields below.</notice>
       <label translate="true">Logo Image</label>
  • Is this work for you properly? Commented Jan 7, 2019 at 9:05
  • Yes it worked for me. Commented Jan 7, 2019 at 9:17
  • 1
    You should not edit core files.
    – ProxiBlue
    Commented Jan 10, 2019 at 12:33
  • @ProxiBlue, You need to add this file in your custom module in this path Vendor/Module/view/adminhtml/ui_component/design_config_form.xml Commented Mar 25, 2019 at 10:20
  • Same way you have to check other files as well ./vendor/magento/module-email/view/adminhtml/ui_component/design_config_form.xml ./vendor/magento/module-catalog/view/adminhtml/ui_component/design_config_form.xml ./vendor/magento/module-backend/view/adminhtml/ui_component/design_config_form.xml ./vendor/magento/module-swatches/view/adminhtml/ui_component/design_config_form.xml ./vendor/magento/module-theme/view/adminhtml/ui_component/design_config_form.xml
    – Jdprasad V
    Commented Mar 13, 2020 at 14:52

Install the 2.3.1 update and it will be fixed. any other way to fix this would be hacky and might break things after updating.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.