Anyone else having problems getting the newly released patch to work? I'm running Magento 188.8.131.52, but it's fully patched up to this most recent patch. I just verified by doing a dry-run patch with SUPEE-5994 to ensure that it was already done.
When I try to run the SUPEE-6285 patch, I get the following:
./PATCH_SUPEE-6285_CE_184.108.40.206_v1-2015-07-07-09-03-34.sh: 14: ./PATCH_SUPEE-6285_CE_220.127.116.11_v1-2015-07-07-09-03-34.sh: 127: not found ./PATCH_SUPEE-6285_CE_18.104.22.168_v1-2015-07-07-09-03-34.sh: 14: ./PATCH_SUPEE-6285_CE_22.214.171.124_v1-2015-07-07-09-03-34.sh: 127: not found ./PATCH_SUPEE-6285_CE_126.96.36.199_v1-2015-07-07-09-03-34.sh: 25: ./PATCH_SUPEE-6285_CE_188.8.131.52_v1-2015-07-07-09-03-34.sh: 0: not found Checking if patch can be applied/reverted successfully... -e ERROR: Patch can't be applied/reverted successfully.
Lines 14 and 25, where the script appears to be having issues, are in the function _check_installed_tools(), so perhaps I'm missing a tool on our server to do the patch. But there isn't any relevant error message to indicate which tool.
A little help please?
Solved! Go to Solution.
Looked through some old threads and found the solution. There was a file that already exists that the script wished to create. I didn't inlcude the full output from the failure of the patch, but these lines were included and important:
The next patch would create the file downloader/Maged/.htaccess, which already exists! Assume -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored
Turns out I just had to remove the downloader/Maged/.htaccess file and then the patch installed without any problems.
I have applied recent security patches and finding that PATCH_SUPEE-6285 is failing on one file which is AuthorizeController.php.
patching file app/code/core/Mage/Oauth/controllers/Adminhtml/Oauth/AuthorizeController.php
Hunk #1 FAILED at 298.
1 out of 1 hunk FAILED -- saving rejects to file app/code/core/Mage/Oauth/controllers/Adminhtml/Oauth/AuthorizeController.php.rej
I have Magento ver 184.108.40.206 installed and I downloaded the following security patches
PATCH_SUPEE-5345_CE_220.127.116.11_v1-2015-02-10-08-11-22 (Applied in February)
PATCH_SUPEE-5994_CE_18.104.22.168_v1-2015-05-15-04-34-46 (Applied in May - note this patch is for magento versions 22.214.171.124 til 126.96.36.199)
Existing lines 294 - 301 in file app/code/core/Mage/Oauth/controllers/Adminhtml/Oauth/AuthorizeController.php are as below;
295 * Reject token authorization simple page
297 public function rejectSimpleAction()
Anyone with any idea as to why this is occuring?
I had the same issue and removing that file allowed it to patch successfully, but why does the scrip just assume no without prompting the user for input?
Hello, we have written quickly a tiny tool to check a bit more ...
feel free do give us feedback if do you think it makes sence :-)
you are welcome to improve our code as well.
Thanks for your reply, but that didn't do it either, the patch still can't be applied as that file is now missing!
The hunk failure is probably due to a line ending issue. Others have fixed it by downloading the full install archive of their version, extracting the file that has the hunk failure and uploading it to their Magento installation where they're trying to apply the patch.
In your case this would be app/code/core/Mage/Oauth/controllers/Adminhtml/Oauth/AuthorizeController.php that you want to extract.
https://www.magentocommerce.com/download and click the Release Archive tab to access full Magento install archives for past versions.
to resolve this problem, comment the 2 lines below in the file PATCH_SUPEE-6285_CE_188.8.131.52_v1-2015-07-10-08-10-09.sh: