8

Details about the problem SUPEE-8788 replaces the old flash uploader with a new uploader system that sits in Mage/Uploader module. By default 1.7.0.2 has got the following code in app/code/core/Mage/Adminhtml/Block/Catalog/Product/Helper/Form/Gallery/Content.php $this->setChild('uploader', $this->getLayout()->createBlock('adminhtml/...


5

SUPEE 8788 V2 fixes the following problems introduced by SUPEE 8788 V1: conflict with 1533 patch conflict with 3941 patch Unsupported data type N error in /lib/Unserialize/Reader/ArrValue.php in 1.9.1.0 and possibly earlier versions If you apply the patch V2 don't forget to follow this procedure: revert SUPEE-8788 v1 revert SUPEE-1533 (if installed) ...


3

Correct me if I'm wrong, but IMHO the Dull Uploader has become redundant after SUPEE-8788, since the purpose of the extension is to replace Flash. Solution: uninstall Dull Uploader.


2

Old post, but in case anyone is looking for a solution when browser is not throwing any console errors, check if you have Dull Uploader installed and disable or remove it. This solved it for me.


2

Fixed - Image Upload issue after PATCH 8788 install of Magento version CE 1.7.0.2 - 1.9.2.4. I was able to fix it,Please Follow following instruction. Step >> 1: After installed security patch 8788 successfully, Please go to admin panel and flush all Magento cache. Then Logout your Admin Panel and Relogin to Admin Panel. Step >> 2: Go to Index ...


2

No, you don't need to install SUPEE-3941 on Magento 1.9.1.0 and later.


2

You can use -R or --revert to revert a patch. For example: ./PATCH_V1.sh -R ./PATCH_V2.sh


2

Fixed - Image Upload issue after PATCH 8788 install of Magento version CE 1.7.0.2 - 1.9.2.4. I was able to fix it,Please Follow following instruction. Step >> 1: After installed security patch 8788 successfully, Please go to admin panel and flush all Magento cache. Then Logout your Admin Panel and Relogin to Admin Panel. Step >> 2: Go to Index ...


2

How do I know what patches that are not installed? Once I install them, how do I know they are actually installed? For this you can use https://github.com/philwinkle/Philwinkle_AppliedPatches that will show all applied patches in footer. Is there a possibility patching can cause issues with the installation (theme & extension) or it is ...


1

Magento scan tool and Magereport performs the same work but in little different way. I would say Magereport is more flexible than Magento scanner. I'll give you an examples here: One of my security patch was detected as failed by Magento and on the same time Magereport was saying passed. After investing a lot of effort and time we find out that Magento ...


1

Just as "answer" ... if you are using PHP7 there are serveral other things that have to be fixed! I strongly recommend using this extension: https://github.com/Inchoo/Inchoo_PHP7/


1

I found the solution, this is a bug in SUPEE-8788 Open samples.phtml inside app/design/adminhtml/default/default/template/downloadable/product/edit/downloadable Find the function remove : function(event){ var element = $(Event.findElement(event, 'tr')); alertAlreadyDisplayed = false; if(element){ element.down('input[type="hidden"]....


1

Apply patch SUPEE-3941 followed by SUPEE-8788 V2. You should be all set!


1

It's look like you have not installed the previous versions of SUPEE patches. You can check SUPEE patches status here magereport. Please apply all previous versions and then install SUPEE-8788. For read about hunk click here Hope this will help you.


1

It's definitely a problem with the patch. SUPEE-8788 v2 provides a new file lib/Unserialize/Reader/Null.php. Please double check that this file is present on your Magento install. If it's not present, that means v2 was not properly installed, thus you need to patch v2 correctly. If it's present, you probably have some sort of compiler that had not been ...


1

Solved First, to get rid of checking file skin/adminhtml/default/default/media/uploaderSingle.swf Reversed (or previously applied) patch detected! I use this solution: just need to zip patch and unzip it on server Then checking file app/locale/en_US/Mage_Media.csv Reversed (or previously applied) patch detected! Assume -R? [n] I remove Mage_Media....


1

I managed to apply correctly the patch. I share my solution hoping it could be useful to someone encountering the same problem. Since I was installing the v2 of the patch without having installed the v1 there is no need to revert the SUPEE-1533 patch. Reverting it without having installed the v1 of SUPEE-8788 causes the problem (Magento 1.9.2.0 SUPEE-8788 ...


1

you can check in this website that how many security patches you missing. I think in mgaento 1.9.2.4 you already have this patch but for safer side you can check.


Only top voted, non community-wiki answers of a minimum length are eligible