SUPEE 8788 AND SUPEE 1533 (Incompatible, Hunk error)

[baghulia]

As previously told, reverting patch #1533 and applying patch #8788 v2 gives and following all the instructions gives me the following error and the patch is not applied at all: @sherrie any idea on how to solve that? it would be much appreciated...

Hunk #1 FAILED at 372.

1 out of 1 hunk FAILED -- saving rejects to file downloader/lib/Mage/HTTP/Client/Curl.php.rej

patching file downloader/template/connect/packages.phtml

patching file js/lib/uploader/flow.min.js

patching file js/lib/uploader/fusty-flow-factory.js

patching file js/lib/uploader/fusty-flow.js

patching file js/mage/adminhtml/product.js

patching file js/mage/adminhtml/uploader/instance.js

patching file lib/Unserialize/Parser.php

patching file lib/Unserialize/Reader/Arr.php

patching file lib/Unserialize/Reader/ArrValue.php

patching file lib/Unserialize/Reader/Null.php

patching file skin/adminhtml/default/default/boxes.css

patching file skin/adminhtml/default/default/media/flex.swf

patching file skin/adminhtml/default/default/media/uploader.swf

patching file skin/adminhtml/default/default/media/uploaderSingle.swf

[baghulia]

@sherrie Any help to overcome the issue found with the patch #8788 on 1.6.2 as it's not possible to install patch #3941

Hunk #1 FAILED at 372.

1 out of 1 hunk FAILED -- saving rejects to file downloader/lib/Mage/HTTP/Client/Curl.php.rej

Thanks

[sherrie]

Hi @baghulia - checking for you.

[sherrie]

@David_Kombinat @baghulia - checking for you.

[SamHagerty]

We had this issue too, nightmare considering we don't even use the downloader.

The way we managed to get round this issue was dumping a fresh 1.8.1.0 downloader folder on before installing patch #3941.

Then once patched #3941, patch #8788 v2 will fail on a few files stating a previously applied patch is detected, change these back to fresh 1.6.2 files.

Then it failed on downloader/Maged/View.php so apply this fix http://magento.stackexchange.com/questions/140742/security-patch-supee-8788-failing-at-downloader-ma...

Following that #8788 v2 will patch successfully, we then just deleted our downloader again!

Yet to find an easier solution thus far.

[kmbt]

@sherrie, we have the patch applied, thanks to the hints from @SamHagerty.

That was really time-consuming. :-/

[baghulia]

@sherrie any news regarding the patch on 1.6.2? should we follow the tricky solution given? Best regards,

[baghulia]

@sherrie any news regarding the patch for 1.6.2.? do we need to follow the tricky solution given by some users on this thread?

[sherrie]

Hi @kmbt, glad you were able to get it sorted - sorry to hear it was so time consuming for you. Are you still looking for a solution @baghulia?

[baghulia]

@sherrie yes, still looking for an official solution, should we try the given solution?