Magento 2 can not upload product imagesmagento 2 Default image file types not acceptableHide products without images (CE 1.9)Magento 1.7 Import: “Invalid image file type.”magento 2 Default image file types not acceptableCreate and Save Simple Products with Configurable Products ImagesUnable to Upload Product Images 1.9.3.3Magento 2- can not upload product imageMagento 2: Do I need to have separate swatches for every configurable product?Magento 2.1 Product Admin Image UploadWe don't recognize or support this file extension type on uploading the product image magento version 2.2.2Images not uploading when going through the process in the Product Images tab

Could gravitational lensing be used to protect a spaceship from a laser?

Were any external disk drives stacked vertically?

Theorems that impeded progress

AES: Why is it a good practice to use only the first 16bytes of a hash for encryption?

Is there a hemisphere-neutral way of specifying a season?

Can a virus destroy the BIOS of a modern computer?

Is it inappropriate for a student to attend their mentor's dissertation defense?

Assassin's bullet with mercury

How do conventional missiles fly?

How could indestructible materials be used in power generation?

How to model explosives?

Can a rocket refuel on Mars from water?

Is "remove commented out code" correct English?

Can I ask the recruiters in my resume to put the reason why I am rejected?

What to put in ESTA if staying in US for a few days before going on to Canada

Combinations of multiple lists

Why does Arabsat 6A need a Falcon Heavy to launch

Is Lorentz symmetry broken if SUSY is broken?

Can one be a co-translator of a book, if he does not know the language that the book is translated into?

Should I tell management that I intend to leave due to bad software development practices?

Arrow those variables!

What is the PIE reconstruction for word-initial alpha with rough breathing?

Is it unprofessional to ask if a job posting on GlassDoor is real?

If a Gelatinous Cube takes up the entire space of a Pit Trap, what happens when a creature falls into the trap but succeeds on the saving throw?



Magento 2 can not upload product images


magento 2 Default image file types not acceptableHide products without images (CE 1.9)Magento 1.7 Import: “Invalid image file type.”magento 2 Default image file types not acceptableCreate and Save Simple Products with Configurable Products ImagesUnable to Upload Product Images 1.9.3.3Magento 2- can not upload product imageMagento 2: Do I need to have separate swatches for every configurable product?Magento 2.1 Product Admin Image UploadWe don't recognize or support this file extension type on uploading the product image magento version 2.2.2Images not uploading when going through the process in the Product Images tab






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








5















Any time I try to add images to a product in Magento 2.1 I get the following error:



Attention: We don't recognize or support this file extension type.



It does not matter what type of image I attempt to upload. I went through the whole list of supported file types. I tried it with a simple product and with a configurable product.



Does anyone know how to fix this issue? This question was asked before here but the answers misunderstood the question and are not helpful.










share|improve this question
























  • Flash is possibly the issue. Browsers are blocking it. Finding I have to use Firefox.

    – user66194
    Mar 29 '18 at 5:47











  • @user66194 - You might be confusing this question with another issue. Magento 2.1+ and 2.2+ does not use flash to upload or display images. You technically could install a third party extension that uses flash for some reason but this is highly unlikely and sounds like a terrible idea; in my case (OP) flash is definitely not the issue, see my answer below.

    – Blizzardengle
    Mar 29 '18 at 6:33


















5















Any time I try to add images to a product in Magento 2.1 I get the following error:



Attention: We don't recognize or support this file extension type.



It does not matter what type of image I attempt to upload. I went through the whole list of supported file types. I tried it with a simple product and with a configurable product.



Does anyone know how to fix this issue? This question was asked before here but the answers misunderstood the question and are not helpful.










share|improve this question
























  • Flash is possibly the issue. Browsers are blocking it. Finding I have to use Firefox.

    – user66194
    Mar 29 '18 at 5:47











  • @user66194 - You might be confusing this question with another issue. Magento 2.1+ and 2.2+ does not use flash to upload or display images. You technically could install a third party extension that uses flash for some reason but this is highly unlikely and sounds like a terrible idea; in my case (OP) flash is definitely not the issue, see my answer below.

    – Blizzardengle
    Mar 29 '18 at 6:33














5












5








5


1






Any time I try to add images to a product in Magento 2.1 I get the following error:



Attention: We don't recognize or support this file extension type.



It does not matter what type of image I attempt to upload. I went through the whole list of supported file types. I tried it with a simple product and with a configurable product.



Does anyone know how to fix this issue? This question was asked before here but the answers misunderstood the question and are not helpful.










share|improve this question
















Any time I try to add images to a product in Magento 2.1 I get the following error:



Attention: We don't recognize or support this file extension type.



It does not matter what type of image I attempt to upload. I went through the whole list of supported file types. I tried it with a simple product and with a configurable product.



Does anyone know how to fix this issue? This question was asked before here but the answers misunderstood the question and are not helpful.







magento-2.0 product-images image-upload






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 '17 at 12:54









Community

1




1










asked Jul 26 '16 at 23:10









BlizzardengleBlizzardengle

3581213




3581213












  • Flash is possibly the issue. Browsers are blocking it. Finding I have to use Firefox.

    – user66194
    Mar 29 '18 at 5:47











  • @user66194 - You might be confusing this question with another issue. Magento 2.1+ and 2.2+ does not use flash to upload or display images. You technically could install a third party extension that uses flash for some reason but this is highly unlikely and sounds like a terrible idea; in my case (OP) flash is definitely not the issue, see my answer below.

    – Blizzardengle
    Mar 29 '18 at 6:33


















  • Flash is possibly the issue. Browsers are blocking it. Finding I have to use Firefox.

    – user66194
    Mar 29 '18 at 5:47











  • @user66194 - You might be confusing this question with another issue. Magento 2.1+ and 2.2+ does not use flash to upload or display images. You technically could install a third party extension that uses flash for some reason but this is highly unlikely and sounds like a terrible idea; in my case (OP) flash is definitely not the issue, see my answer below.

    – Blizzardengle
    Mar 29 '18 at 6:33

















Flash is possibly the issue. Browsers are blocking it. Finding I have to use Firefox.

– user66194
Mar 29 '18 at 5:47





Flash is possibly the issue. Browsers are blocking it. Finding I have to use Firefox.

– user66194
Mar 29 '18 at 5:47













@user66194 - You might be confusing this question with another issue. Magento 2.1+ and 2.2+ does not use flash to upload or display images. You technically could install a third party extension that uses flash for some reason but this is highly unlikely and sounds like a terrible idea; in my case (OP) flash is definitely not the issue, see my answer below.

– Blizzardengle
Mar 29 '18 at 6:33






@user66194 - You might be confusing this question with another issue. Magento 2.1+ and 2.2+ does not use flash to upload or display images. You technically could install a third party extension that uses flash for some reason but this is highly unlikely and sounds like a terrible idea; in my case (OP) flash is definitely not the issue, see my answer below.

– Blizzardengle
Mar 29 '18 at 6:33











7 Answers
7






active

oldest

votes


















18














Solved

This error can be caused by several server configuration issues. Each error will always present itself with the same generic warning from Magento 2: Attention: We don't recognize or support this file extension type. If your using Magento 2.2.0+ the error may be worded differently. Below are the most common server settings that are causing this error. There may be more than this list but these are all I have personally tested.



1) Permission Problem

You may get an error along the lines of "Can not create directory pub/media/tmp" or you may notice after examining the XHR summary in developer tools that a 200 success code is returned but no data was saved to the server. The easiest way to test this to check your servers permissions and make sure all the directories, especially everything under pub/media is 755. You may have a mix of the following issues as well so do not stop troubleshooting permissions until you check them as well.



2) Missing Write Permissions to Upload Directory / Missing Directory

PHP needs to use the servers temporary upload directory when uploading files to the server. Make sure that your server has a temporary upload directory setup and is writable by the Magento user; whichever user you are using for your Magento website. Most hosting providers have this setup for you but some may lock down this feature or may be missing a default setting. Private servers sometimes rely on you choosing the temporary upload directory per domain and then defaulting to a generic location if you failed to choose one. Look in your php.ini (phpinfo) for upload_tmp_dir. No value means the server will use the default if it can find any.



3) Insufficient max file size and post file size

In your php.ini file you need to correctly set your upload_max_filesize and post_max_size. If any image or any upload of images exceeds these settings you will get the error from the OP. Remember this rule:



post_max_size must be >= upload_max_filesize



Also note that your web host will most likely not warn you if you entered an incorrect value here. You could mistype the value or choose a size the web host does not allow. Test for this.



4) PHP GD (image processing) extension missing

You should have been warned during install if you were missing this extension but PHP upgrades on your server could have disabled it. The fastest way to check this setting is to look through the print out of phpinfo() but you can look it up in cPanel or your Apache/PHP provisioning on an Apache server.



5) PHP ImageMagick (image processing) extension missing

Starting with Magento 2.2.0+ Magento would like to use ImageMagick as well. The documentation is not to clear but it appears you can use one or both of these PHP extensions. If you upgrade to or install PHP 7+ on your server there is a chance it will disable GB and enable ImageMagick depending on how your provisioning your server. Just check that one if not both of them is enabled and working correctly.



Test Script

The following is a PHP script you can use to test for some of these issues. Make a simple HTML form with one file input field named upfile and set the form action to submit to wherever you place this script on your server. You will need to create an uploads directory in the same directory as this script. It is not my code, it was originally posted to the PHP Manual by CertaiN.



<?php

header('Content-Type: text/plain; charset=utf-8');

try catch (RuntimeException $e)

echo $e->getMessage();



?>





share|improve this answer




















  • 1





    Considering Imagemagick one must check if "ImageMagick supported formats" list is filled with image extensions on phpinfo() page. My supported formats gone after updating ImageMagick.

    – Gediminas
    Oct 26 '18 at 12:39


















3














I fixed it in cPanel > PHP Selector extensions when I had the same error:



  1. Select gd

  2. Select xsl

Then I tried to upload images again and this error is not there anymore.



enter image description here






share|improve this answer
































    3














    In our experience this can also be caused by the server/hosting being out of space (i.e. disk full).






    share|improve this answer






























      1














      Check phpinfo() page, if file_uploads is off, set file_uploads on
      enter image description here






      share|improve this answer






























        1














        I did this for me :



        sudo chmod -R 777 pub/media/tmp


        It is working now






        share|improve this answer























        • This falls under point 1 in my answer. You should use 755 instead of 777.

          – Blizzardengle
          Oct 10 '18 at 6:31


















        0














        Probably is a permission problem. Check the ajax response when you try to upload the image.
        If returns an error with message "Can not create directory pub/media/tmp...", then you just have to set correct permissions for "pub/media" directory.






        share|improve this answer























        • No errors are reported what-so-ever. Console or back-end logs. I tested your theory about permission issues and everything is working as expected. No permission issues, no errors, status 200 always returns. It doesn't seem to be a permissions problem. You can see track the progress of this bug here: github.com/magento/magento2/issues/5845

          – Blizzardengle
          Aug 2 '16 at 17:38


















        0














        I ran into same issue,suddenly magento 2 start getting message "We don't recognize or support this file extension type."
        I solved it by



        1. clean cache(php bin/magento cache:clean)

        2. flush cache(php bin/magento cache:flush)

        3. reindex (php bin/magento indexer:reindex)

        4. logout from the backend and login again





        share|improve this answer























          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "479"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f127586%2fmagento-2-can-not-upload-product-images%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          7 Answers
          7






          active

          oldest

          votes








          7 Answers
          7






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          18














          Solved

          This error can be caused by several server configuration issues. Each error will always present itself with the same generic warning from Magento 2: Attention: We don't recognize or support this file extension type. If your using Magento 2.2.0+ the error may be worded differently. Below are the most common server settings that are causing this error. There may be more than this list but these are all I have personally tested.



          1) Permission Problem

          You may get an error along the lines of "Can not create directory pub/media/tmp" or you may notice after examining the XHR summary in developer tools that a 200 success code is returned but no data was saved to the server. The easiest way to test this to check your servers permissions and make sure all the directories, especially everything under pub/media is 755. You may have a mix of the following issues as well so do not stop troubleshooting permissions until you check them as well.



          2) Missing Write Permissions to Upload Directory / Missing Directory

          PHP needs to use the servers temporary upload directory when uploading files to the server. Make sure that your server has a temporary upload directory setup and is writable by the Magento user; whichever user you are using for your Magento website. Most hosting providers have this setup for you but some may lock down this feature or may be missing a default setting. Private servers sometimes rely on you choosing the temporary upload directory per domain and then defaulting to a generic location if you failed to choose one. Look in your php.ini (phpinfo) for upload_tmp_dir. No value means the server will use the default if it can find any.



          3) Insufficient max file size and post file size

          In your php.ini file you need to correctly set your upload_max_filesize and post_max_size. If any image or any upload of images exceeds these settings you will get the error from the OP. Remember this rule:



          post_max_size must be >= upload_max_filesize



          Also note that your web host will most likely not warn you if you entered an incorrect value here. You could mistype the value or choose a size the web host does not allow. Test for this.



          4) PHP GD (image processing) extension missing

          You should have been warned during install if you were missing this extension but PHP upgrades on your server could have disabled it. The fastest way to check this setting is to look through the print out of phpinfo() but you can look it up in cPanel or your Apache/PHP provisioning on an Apache server.



          5) PHP ImageMagick (image processing) extension missing

          Starting with Magento 2.2.0+ Magento would like to use ImageMagick as well. The documentation is not to clear but it appears you can use one or both of these PHP extensions. If you upgrade to or install PHP 7+ on your server there is a chance it will disable GB and enable ImageMagick depending on how your provisioning your server. Just check that one if not both of them is enabled and working correctly.



          Test Script

          The following is a PHP script you can use to test for some of these issues. Make a simple HTML form with one file input field named upfile and set the form action to submit to wherever you place this script on your server. You will need to create an uploads directory in the same directory as this script. It is not my code, it was originally posted to the PHP Manual by CertaiN.



          <?php

          header('Content-Type: text/plain; charset=utf-8');

          try catch (RuntimeException $e)

          echo $e->getMessage();



          ?>





          share|improve this answer




















          • 1





            Considering Imagemagick one must check if "ImageMagick supported formats" list is filled with image extensions on phpinfo() page. My supported formats gone after updating ImageMagick.

            – Gediminas
            Oct 26 '18 at 12:39















          18














          Solved

          This error can be caused by several server configuration issues. Each error will always present itself with the same generic warning from Magento 2: Attention: We don't recognize or support this file extension type. If your using Magento 2.2.0+ the error may be worded differently. Below are the most common server settings that are causing this error. There may be more than this list but these are all I have personally tested.



          1) Permission Problem

          You may get an error along the lines of "Can not create directory pub/media/tmp" or you may notice after examining the XHR summary in developer tools that a 200 success code is returned but no data was saved to the server. The easiest way to test this to check your servers permissions and make sure all the directories, especially everything under pub/media is 755. You may have a mix of the following issues as well so do not stop troubleshooting permissions until you check them as well.



          2) Missing Write Permissions to Upload Directory / Missing Directory

          PHP needs to use the servers temporary upload directory when uploading files to the server. Make sure that your server has a temporary upload directory setup and is writable by the Magento user; whichever user you are using for your Magento website. Most hosting providers have this setup for you but some may lock down this feature or may be missing a default setting. Private servers sometimes rely on you choosing the temporary upload directory per domain and then defaulting to a generic location if you failed to choose one. Look in your php.ini (phpinfo) for upload_tmp_dir. No value means the server will use the default if it can find any.



          3) Insufficient max file size and post file size

          In your php.ini file you need to correctly set your upload_max_filesize and post_max_size. If any image or any upload of images exceeds these settings you will get the error from the OP. Remember this rule:



          post_max_size must be >= upload_max_filesize



          Also note that your web host will most likely not warn you if you entered an incorrect value here. You could mistype the value or choose a size the web host does not allow. Test for this.



          4) PHP GD (image processing) extension missing

          You should have been warned during install if you were missing this extension but PHP upgrades on your server could have disabled it. The fastest way to check this setting is to look through the print out of phpinfo() but you can look it up in cPanel or your Apache/PHP provisioning on an Apache server.



          5) PHP ImageMagick (image processing) extension missing

          Starting with Magento 2.2.0+ Magento would like to use ImageMagick as well. The documentation is not to clear but it appears you can use one or both of these PHP extensions. If you upgrade to or install PHP 7+ on your server there is a chance it will disable GB and enable ImageMagick depending on how your provisioning your server. Just check that one if not both of them is enabled and working correctly.



          Test Script

          The following is a PHP script you can use to test for some of these issues. Make a simple HTML form with one file input field named upfile and set the form action to submit to wherever you place this script on your server. You will need to create an uploads directory in the same directory as this script. It is not my code, it was originally posted to the PHP Manual by CertaiN.



          <?php

          header('Content-Type: text/plain; charset=utf-8');

          try catch (RuntimeException $e)

          echo $e->getMessage();



          ?>





          share|improve this answer




















          • 1





            Considering Imagemagick one must check if "ImageMagick supported formats" list is filled with image extensions on phpinfo() page. My supported formats gone after updating ImageMagick.

            – Gediminas
            Oct 26 '18 at 12:39













          18












          18








          18







          Solved

          This error can be caused by several server configuration issues. Each error will always present itself with the same generic warning from Magento 2: Attention: We don't recognize or support this file extension type. If your using Magento 2.2.0+ the error may be worded differently. Below are the most common server settings that are causing this error. There may be more than this list but these are all I have personally tested.



          1) Permission Problem

          You may get an error along the lines of "Can not create directory pub/media/tmp" or you may notice after examining the XHR summary in developer tools that a 200 success code is returned but no data was saved to the server. The easiest way to test this to check your servers permissions and make sure all the directories, especially everything under pub/media is 755. You may have a mix of the following issues as well so do not stop troubleshooting permissions until you check them as well.



          2) Missing Write Permissions to Upload Directory / Missing Directory

          PHP needs to use the servers temporary upload directory when uploading files to the server. Make sure that your server has a temporary upload directory setup and is writable by the Magento user; whichever user you are using for your Magento website. Most hosting providers have this setup for you but some may lock down this feature or may be missing a default setting. Private servers sometimes rely on you choosing the temporary upload directory per domain and then defaulting to a generic location if you failed to choose one. Look in your php.ini (phpinfo) for upload_tmp_dir. No value means the server will use the default if it can find any.



          3) Insufficient max file size and post file size

          In your php.ini file you need to correctly set your upload_max_filesize and post_max_size. If any image or any upload of images exceeds these settings you will get the error from the OP. Remember this rule:



          post_max_size must be >= upload_max_filesize



          Also note that your web host will most likely not warn you if you entered an incorrect value here. You could mistype the value or choose a size the web host does not allow. Test for this.



          4) PHP GD (image processing) extension missing

          You should have been warned during install if you were missing this extension but PHP upgrades on your server could have disabled it. The fastest way to check this setting is to look through the print out of phpinfo() but you can look it up in cPanel or your Apache/PHP provisioning on an Apache server.



          5) PHP ImageMagick (image processing) extension missing

          Starting with Magento 2.2.0+ Magento would like to use ImageMagick as well. The documentation is not to clear but it appears you can use one or both of these PHP extensions. If you upgrade to or install PHP 7+ on your server there is a chance it will disable GB and enable ImageMagick depending on how your provisioning your server. Just check that one if not both of them is enabled and working correctly.



          Test Script

          The following is a PHP script you can use to test for some of these issues. Make a simple HTML form with one file input field named upfile and set the form action to submit to wherever you place this script on your server. You will need to create an uploads directory in the same directory as this script. It is not my code, it was originally posted to the PHP Manual by CertaiN.



          <?php

          header('Content-Type: text/plain; charset=utf-8');

          try catch (RuntimeException $e)

          echo $e->getMessage();



          ?>





          share|improve this answer















          Solved

          This error can be caused by several server configuration issues. Each error will always present itself with the same generic warning from Magento 2: Attention: We don't recognize or support this file extension type. If your using Magento 2.2.0+ the error may be worded differently. Below are the most common server settings that are causing this error. There may be more than this list but these are all I have personally tested.



          1) Permission Problem

          You may get an error along the lines of "Can not create directory pub/media/tmp" or you may notice after examining the XHR summary in developer tools that a 200 success code is returned but no data was saved to the server. The easiest way to test this to check your servers permissions and make sure all the directories, especially everything under pub/media is 755. You may have a mix of the following issues as well so do not stop troubleshooting permissions until you check them as well.



          2) Missing Write Permissions to Upload Directory / Missing Directory

          PHP needs to use the servers temporary upload directory when uploading files to the server. Make sure that your server has a temporary upload directory setup and is writable by the Magento user; whichever user you are using for your Magento website. Most hosting providers have this setup for you but some may lock down this feature or may be missing a default setting. Private servers sometimes rely on you choosing the temporary upload directory per domain and then defaulting to a generic location if you failed to choose one. Look in your php.ini (phpinfo) for upload_tmp_dir. No value means the server will use the default if it can find any.



          3) Insufficient max file size and post file size

          In your php.ini file you need to correctly set your upload_max_filesize and post_max_size. If any image or any upload of images exceeds these settings you will get the error from the OP. Remember this rule:



          post_max_size must be >= upload_max_filesize



          Also note that your web host will most likely not warn you if you entered an incorrect value here. You could mistype the value or choose a size the web host does not allow. Test for this.



          4) PHP GD (image processing) extension missing

          You should have been warned during install if you were missing this extension but PHP upgrades on your server could have disabled it. The fastest way to check this setting is to look through the print out of phpinfo() but you can look it up in cPanel or your Apache/PHP provisioning on an Apache server.



          5) PHP ImageMagick (image processing) extension missing

          Starting with Magento 2.2.0+ Magento would like to use ImageMagick as well. The documentation is not to clear but it appears you can use one or both of these PHP extensions. If you upgrade to or install PHP 7+ on your server there is a chance it will disable GB and enable ImageMagick depending on how your provisioning your server. Just check that one if not both of them is enabled and working correctly.



          Test Script

          The following is a PHP script you can use to test for some of these issues. Make a simple HTML form with one file input field named upfile and set the form action to submit to wherever you place this script on your server. You will need to create an uploads directory in the same directory as this script. It is not my code, it was originally posted to the PHP Manual by CertaiN.



          <?php

          header('Content-Type: text/plain; charset=utf-8');

          try catch (RuntimeException $e)

          echo $e->getMessage();



          ?>






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 13 '18 at 0:07

























          answered Aug 5 '16 at 23:45









          BlizzardengleBlizzardengle

          3581213




          3581213







          • 1





            Considering Imagemagick one must check if "ImageMagick supported formats" list is filled with image extensions on phpinfo() page. My supported formats gone after updating ImageMagick.

            – Gediminas
            Oct 26 '18 at 12:39












          • 1





            Considering Imagemagick one must check if "ImageMagick supported formats" list is filled with image extensions on phpinfo() page. My supported formats gone after updating ImageMagick.

            – Gediminas
            Oct 26 '18 at 12:39







          1




          1





          Considering Imagemagick one must check if "ImageMagick supported formats" list is filled with image extensions on phpinfo() page. My supported formats gone after updating ImageMagick.

          – Gediminas
          Oct 26 '18 at 12:39





          Considering Imagemagick one must check if "ImageMagick supported formats" list is filled with image extensions on phpinfo() page. My supported formats gone after updating ImageMagick.

          – Gediminas
          Oct 26 '18 at 12:39













          3














          I fixed it in cPanel > PHP Selector extensions when I had the same error:



          1. Select gd

          2. Select xsl

          Then I tried to upload images again and this error is not there anymore.



          enter image description here






          share|improve this answer





























            3














            I fixed it in cPanel > PHP Selector extensions when I had the same error:



            1. Select gd

            2. Select xsl

            Then I tried to upload images again and this error is not there anymore.



            enter image description here






            share|improve this answer



























              3












              3








              3







              I fixed it in cPanel > PHP Selector extensions when I had the same error:



              1. Select gd

              2. Select xsl

              Then I tried to upload images again and this error is not there anymore.



              enter image description here






              share|improve this answer















              I fixed it in cPanel > PHP Selector extensions when I had the same error:



              1. Select gd

              2. Select xsl

              Then I tried to upload images again and this error is not there anymore.



              enter image description here







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jan 13 '17 at 14:42









              7ochem

              5,83493768




              5,83493768










              answered Jan 13 '17 at 13:46









              Asian Trade ZoneAsian Trade Zone

              311




              311





















                  3














                  In our experience this can also be caused by the server/hosting being out of space (i.e. disk full).






                  share|improve this answer



























                    3














                    In our experience this can also be caused by the server/hosting being out of space (i.e. disk full).






                    share|improve this answer

























                      3












                      3








                      3







                      In our experience this can also be caused by the server/hosting being out of space (i.e. disk full).






                      share|improve this answer













                      In our experience this can also be caused by the server/hosting being out of space (i.e. disk full).







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jun 13 '17 at 15:52









                      YorkieMagentoYorkieMagento

                      48431442




                      48431442





















                          1














                          Check phpinfo() page, if file_uploads is off, set file_uploads on
                          enter image description here






                          share|improve this answer



























                            1














                            Check phpinfo() page, if file_uploads is off, set file_uploads on
                            enter image description here






                            share|improve this answer

























                              1












                              1








                              1







                              Check phpinfo() page, if file_uploads is off, set file_uploads on
                              enter image description here






                              share|improve this answer













                              Check phpinfo() page, if file_uploads is off, set file_uploads on
                              enter image description here







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Aug 13 '18 at 16:09









                              LilyLily

                              113




                              113





















                                  1














                                  I did this for me :



                                  sudo chmod -R 777 pub/media/tmp


                                  It is working now






                                  share|improve this answer























                                  • This falls under point 1 in my answer. You should use 755 instead of 777.

                                    – Blizzardengle
                                    Oct 10 '18 at 6:31















                                  1














                                  I did this for me :



                                  sudo chmod -R 777 pub/media/tmp


                                  It is working now






                                  share|improve this answer























                                  • This falls under point 1 in my answer. You should use 755 instead of 777.

                                    – Blizzardengle
                                    Oct 10 '18 at 6:31













                                  1












                                  1








                                  1







                                  I did this for me :



                                  sudo chmod -R 777 pub/media/tmp


                                  It is working now






                                  share|improve this answer













                                  I did this for me :



                                  sudo chmod -R 777 pub/media/tmp


                                  It is working now







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Oct 10 '18 at 5:27









                                  Rija CloudRija Cloud

                                  213




                                  213












                                  • This falls under point 1 in my answer. You should use 755 instead of 777.

                                    – Blizzardengle
                                    Oct 10 '18 at 6:31

















                                  • This falls under point 1 in my answer. You should use 755 instead of 777.

                                    – Blizzardengle
                                    Oct 10 '18 at 6:31
















                                  This falls under point 1 in my answer. You should use 755 instead of 777.

                                  – Blizzardengle
                                  Oct 10 '18 at 6:31





                                  This falls under point 1 in my answer. You should use 755 instead of 777.

                                  – Blizzardengle
                                  Oct 10 '18 at 6:31











                                  0














                                  Probably is a permission problem. Check the ajax response when you try to upload the image.
                                  If returns an error with message "Can not create directory pub/media/tmp...", then you just have to set correct permissions for "pub/media" directory.






                                  share|improve this answer























                                  • No errors are reported what-so-ever. Console or back-end logs. I tested your theory about permission issues and everything is working as expected. No permission issues, no errors, status 200 always returns. It doesn't seem to be a permissions problem. You can see track the progress of this bug here: github.com/magento/magento2/issues/5845

                                    – Blizzardengle
                                    Aug 2 '16 at 17:38















                                  0














                                  Probably is a permission problem. Check the ajax response when you try to upload the image.
                                  If returns an error with message "Can not create directory pub/media/tmp...", then you just have to set correct permissions for "pub/media" directory.






                                  share|improve this answer























                                  • No errors are reported what-so-ever. Console or back-end logs. I tested your theory about permission issues and everything is working as expected. No permission issues, no errors, status 200 always returns. It doesn't seem to be a permissions problem. You can see track the progress of this bug here: github.com/magento/magento2/issues/5845

                                    – Blizzardengle
                                    Aug 2 '16 at 17:38













                                  0












                                  0








                                  0







                                  Probably is a permission problem. Check the ajax response when you try to upload the image.
                                  If returns an error with message "Can not create directory pub/media/tmp...", then you just have to set correct permissions for "pub/media" directory.






                                  share|improve this answer













                                  Probably is a permission problem. Check the ajax response when you try to upload the image.
                                  If returns an error with message "Can not create directory pub/media/tmp...", then you just have to set correct permissions for "pub/media" directory.







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Aug 2 '16 at 9:27









                                  user14286user14286

                                  1




                                  1












                                  • No errors are reported what-so-ever. Console or back-end logs. I tested your theory about permission issues and everything is working as expected. No permission issues, no errors, status 200 always returns. It doesn't seem to be a permissions problem. You can see track the progress of this bug here: github.com/magento/magento2/issues/5845

                                    – Blizzardengle
                                    Aug 2 '16 at 17:38

















                                  • No errors are reported what-so-ever. Console or back-end logs. I tested your theory about permission issues and everything is working as expected. No permission issues, no errors, status 200 always returns. It doesn't seem to be a permissions problem. You can see track the progress of this bug here: github.com/magento/magento2/issues/5845

                                    – Blizzardengle
                                    Aug 2 '16 at 17:38
















                                  No errors are reported what-so-ever. Console or back-end logs. I tested your theory about permission issues and everything is working as expected. No permission issues, no errors, status 200 always returns. It doesn't seem to be a permissions problem. You can see track the progress of this bug here: github.com/magento/magento2/issues/5845

                                  – Blizzardengle
                                  Aug 2 '16 at 17:38





                                  No errors are reported what-so-ever. Console or back-end logs. I tested your theory about permission issues and everything is working as expected. No permission issues, no errors, status 200 always returns. It doesn't seem to be a permissions problem. You can see track the progress of this bug here: github.com/magento/magento2/issues/5845

                                  – Blizzardengle
                                  Aug 2 '16 at 17:38











                                  0














                                  I ran into same issue,suddenly magento 2 start getting message "We don't recognize or support this file extension type."
                                  I solved it by



                                  1. clean cache(php bin/magento cache:clean)

                                  2. flush cache(php bin/magento cache:flush)

                                  3. reindex (php bin/magento indexer:reindex)

                                  4. logout from the backend and login again





                                  share|improve this answer



























                                    0














                                    I ran into same issue,suddenly magento 2 start getting message "We don't recognize or support this file extension type."
                                    I solved it by



                                    1. clean cache(php bin/magento cache:clean)

                                    2. flush cache(php bin/magento cache:flush)

                                    3. reindex (php bin/magento indexer:reindex)

                                    4. logout from the backend and login again





                                    share|improve this answer

























                                      0












                                      0








                                      0







                                      I ran into same issue,suddenly magento 2 start getting message "We don't recognize or support this file extension type."
                                      I solved it by



                                      1. clean cache(php bin/magento cache:clean)

                                      2. flush cache(php bin/magento cache:flush)

                                      3. reindex (php bin/magento indexer:reindex)

                                      4. logout from the backend and login again





                                      share|improve this answer













                                      I ran into same issue,suddenly magento 2 start getting message "We don't recognize or support this file extension type."
                                      I solved it by



                                      1. clean cache(php bin/magento cache:clean)

                                      2. flush cache(php bin/magento cache:flush)

                                      3. reindex (php bin/magento indexer:reindex)

                                      4. logout from the backend and login again






                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered 5 hours ago









                                      Muhammad AyazMuhammad Ayaz

                                      1818




                                      1818



























                                          draft saved

                                          draft discarded
















































                                          Thanks for contributing an answer to Magento Stack Exchange!


                                          • Please be sure to answer the question. Provide details and share your research!

                                          But avoid


                                          • Asking for help, clarification, or responding to other answers.

                                          • Making statements based on opinion; back them up with references or personal experience.

                                          To learn more, see our tips on writing great answers.




                                          draft saved


                                          draft discarded














                                          StackExchange.ready(
                                          function ()
                                          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f127586%2fmagento-2-can-not-upload-product-images%23new-answer', 'question_page');

                                          );

                                          Post as a guest















                                          Required, but never shown





















































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown

































                                          Required, but never shown














                                          Required, but never shown












                                          Required, but never shown







                                          Required, but never shown







                                          Popular posts from this blog

                                          Disable / Remove link to Product Items in Cart Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How can I limit products that can be bought / added to cart?Remove item from cartHide “Add to Cart” button if specific products are already in cart“Prettifying” the custom options in cart pageCreate link in cart sidebar to view all added items After limit reachedLink products together in checkout/cartHow to Get product from cart and add it againHide action-edit on cart page if simple productRemoving Cart items - ObserverRemove wishlist items when added to cart

                                          Helsingin valtaus Sisällysluettelo Taustaa | Yleistä sotatoimista | Osapuolet | Taistelut Helsingin ympäristössä | Punaisten antautumissuunnitelma | Taistelujen kulku Helsingissä | Valtauksen jälkeen | Tappiot | Muistaminen | Kirjallisuutta | Lähteet | Aiheesta muualla | NavigointivalikkoTeoksen verkkoversioTeoksen verkkoversioGoogle BooksSisällissota Helsingissä päättyi tasan 95 vuotta sittenSaksalaisten ylivoima jyräsi punaisen HelsinginSuomalaiset kuvaavat sotien jälkiä kaupungeissa – katso kuvat ja tarinat tutuilta kulmiltaHelsingin valtaus 90 vuotta sittenSaksalaiset valtasivat HelsinginHyökkäys HelsinkiinHelsingin valtaus 12.–13.4. 1918Saksalaiset käyttivät ihmiskilpiä Helsingin valtauksessa 1918Teoksen verkkoversioTeoksen verkkoversioSaksalaiset hyökkäävät Etelä-SuomeenTaistelut LeppävaarassaSotilaat ja taistelutLeppävaara 1918 huhtikuussa. KapinatarinaHelsingin taistelut 1918Saksalaisten voitonparaati HelsingissäHelsingin valtausta juhlittiinSaksalaisten Helsinki vuonna 1918Helsingin taistelussa kaatuneet valkokaartilaisetHelsinkiin haudatut taisteluissa kaatuneet punaiset12.4.1918 Helsingin valtauksessa saksalaiset apujoukot vapauttavat kaupunginVapaussodan muistomerkkejä Helsingissä ja pääkaupunkiseudullaCrescendo / Vuoden 1918 Kansalaissodan uhrien muistomerkkim

                                          Adjektiivitarina Tarinan tekeminen | Esimerkki: ennen | Esimerkki: jälkeen | Navigointivalikko