cancel
Showing results for 
Search instead for 
Did you mean: 

1.9.1.0 applying patch 6788 hunk failed

SOLVED

1.9.1.0 applying patch 6788 hunk failed

checking file .htaccess
Hunk #1 FAILED at 207.
1 out of 1 hunk FAILED
checking file .htaccess.sample
checking file app/code/core/Mage/Admin/Model/Block.php
checking file app/code/core/Mage/Admin/Model/Resource/Block.php
checking file app/code/core/Mage/Admin/Model/Resource/Block/Collection.php
checking file app/code/core/Mage/Admin/Model/Resource/Variable.php
checking file app/code/core/Mage/Admin/Model/Resource/Variable/Collection.php
checking file app/code/core/Mage/Admin/Model/Variable.php
checking file app/code/core/Mage/Admin/etc/config.xml
checking file app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.1-1.6.1.2.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Block.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Block/Edit.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Block/Edit/Form.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Block/Grid.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Variable.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Variable/Edit.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Variable/Edit/Form.php
checking file app/code/core/Mage/Adminhtml/Block/Permissions/Variable/Grid.php
checking file app/code/core/Mage/Adminhtml/controllers/Permissions/BlockController.php
checking file app/code/core/Mage/Adminhtml/controllers/Permissions/VariableController.php
checking file app/code/core/Mage/Adminhtml/etc/adminhtml.xml
checking file app/code/core/Mage/Catalog/Model/Product/Option/Type/File.php
checking file app/code/core/Mage/Core/Controller/Request/Http.php
checking file app/code/core/Mage/Core/Controller/Varien/Router/Admin.php
checking file app/code/core/Mage/Core/Helper/UnserializeArray.php
checking file app/code/core/Mage/Core/Model/Email/Template/Filter.php
checking file app/code/core/Mage/Core/Model/Resource/Setup.php
checking file app/code/core/Mage/Customer/Block/Account/Changeforgotten.php
checking file app/code/core/Mage/Customer/Block/Account/Resetpassword.php
checking file app/code/core/Mage/Customer/controllers/AccountController.php
checking file app/code/core/Mage/Downloadable/Model/Product/Type.php
checking file app/code/core/Mage/Eav/Model/Resource/Attribute/Collection.php
checking file app/code/core/Mage/Sales/Model/Resource/Order/Item/Collection.php
checking file app/code/core/Mage/Sales/controllers/DownloadController.php
checking file app/code/core/Mage/SalesRule/Model/Resource/Coupon/Collection.php
checking file app/code/core/Zend/XmlRpc/Request.php
checking file app/code/core/Zend/XmlRpc/Response.php
checking file app/design/adminhtml/default/default/layout/admin.xml
checking file app/design/frontend/base/default/layout/customer.xml
checking file app/design/frontend/base/default/template/customer/form/register.phtml
checking file app/design/frontend/base/default/template/customer/form/resetforgottenpassword.phtml
checking file app/design/frontend/base/default/template/page/js/cookie.phtml
checking file app/design/frontend/base/default/template/persistent/customer/form/register.phtml
checking file app/design/frontend/default/iphone/layout/customer.xml
checking file app/design/frontend/default/modern/layout/customer.xml
checking file app/design/frontend/rwd/default/layout/customer.xml
checking file app/design/frontend/rwd/default/template/customer/form/resetforgottenpassword.phtml

How do I go about determining what this issue is?  Line 207 in which file, I've checked the line in the patch file and its a comment line.

27 REPLIES

Re: 1.9.1.0 applying patch 6788 hunk failed

checking file .htaccess  <=== THIS!
Hunk #1 FAILED at 207. 1 out of 1 hunk FAILED

 

NOTE: YOU SHOULD BE DOING ALL THIS FIRST ON YOUR STAGING SERVER AND THEN REFLECTING CHANGES TO LIVE.

You have a modified Magento root .htaccess file.

Patch SUPEE-6788 DIES immedately upon finding a non-stock Magento root .htaccess file.

 

Back up your current copy of .htaccess twice for luck and create the file magento.flag in your Magento root directory

Go to the Magento download page, grab the installer for your version (1.9.1.0 may be in the release archive) and extract a brand new copy. On the server where you're trying to apply the patch, overwrite your .htaccess file with the stock copy.

 

Apply the patch.


 

Snag a copy of the patched .htaccess, view it for changes (prevents access to cron.php) and modify your saved running version.

 

Overwrite your .htaccess file with the modifed running version, remove maintenance.flag file and test your site for operation

 

Basic summary, remove your .htaccess modifications, patch your Magento installation and then patch your patched .htaccess.

 

Re: 1.9.1.0 applying patch 6788 hunk failed

This affects 1.7.0.2 as well.  My .htaccess was previously modified and .htaccess.sample had been removed.  Restoring these files to their stock 1.7.0.2 versions allowed the patch to succeed.

 

Here are the lines the patch adds to .htaccess (1.7.0.2, other versions may differ)--in my case I've merged these into my customized .htaccess:

 

    <Files cron.php>

############################################
## uncomment next lines to enable cron access with base HTTP authorization
## http://httpd.apache.org/docs/2.2/howto/auth.html
##
## Warning: .htpasswd file should be placed somewhere not accessible from the web.
## This is so that folks cannot download the password file.
## For example, if your documents are served out of /usr/local/apache/htdocs
## you might want to put the password file(s) in /usr/local/apache/.

        #AuthName "Cron auth"
        #AuthUserFile ../.htpasswd
        #AuthType basic
        #Require valid-user

############################################

        Order allow,deny
        Deny from all

  </Files>

Re: 1.9.1.0 applying patch 6788 hunk failed

I use nginx and it is no good idea to make patch with "die" if no .htaccess.

I downloaded my mageno version package and copy .htacess and .htaccess.sample... then patch successfully applied.

Nevertheless, it was uncomfortable.

Re: 1.9.1.0 applying patch 6788 hunk failed

especially when nginx in magento system requirements.

but its just a patch, right? Smiley Happy

------------
MagenX - Magento and Server optimization

Re: 1.9.1.0 applying patch 6788 hunk failed

Hi,

 

I corrected the hunk failed with .htaccess following the explanation.

 

I have an another hunk failed 

 

checking file app/code/core/Mage/Core/Controller/Varien/Router/Admin.php
Hunk #1 FAILED at 131.
1 out of 1 hunk FAILED

When I check this file and compare with a fresh magento the file are identical

 

Have you have any idea ?

 

Thanks

Re: 1.9.1.0 applying patch 6788 hunk failed

I have the same error as davine_rugby after fixing the .htaccess. Does anyone have a solution for this?

Re: 1.9.1.0 applying patch 6788 hunk failed

I have the same issue. app/code/core/Mage/Core/Controller/Varien/Router/Admin.php is unchanged. So I downloaded a fresh 1.7.0.2 and tried to apply the patch. I get the same results. Patch doesn't seem to work completely. The security option that finally enables the changes does not appear in backend either. So I manually edited that file. Only change seems to be a new function (addModule). But that new option still does not appear.

Re: 1.9.1.0 applying patch 6788 hunk failed

Thanks for this .. Smiley Happy

Re: 1.9.1.0 applying patch 6788 hunk failed

I'm also stuck at 1.9.1.0

 

When did I alter the .htaccess? I don't really remember. 

 

Could it be due to earlier patches applied? I've applied the previous patches without upgrading the magento system