cancel
Showing results for 
Search instead for 
Did you mean: 

1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

SOLVED

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

@sherrie

 

Correct, self inflicted wound, once fixed, the 1.6.2.0 SUPEE-6788 patch applied perfectly as downloaded.

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

Thanks for you comments chiefair...

 

 

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

Patch applied successfully but not the new security functions on my backend...

 

Apparently all the other patches were applied as well...

 

Maybe applying the 1.9.2 not correct file previously uploaded caused some serious issue...

 

Keep digging into it..

 

 

 

 

 

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

Anyone has an idea about what's going on? It seem like the patch was not applied but indeed it was... as previously said all the others previous patches were applied ..

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

The htaccess files were modified, so I downloaded the original files and upload it to the root.... Then I've tried to apply the patch again and get the following error ... any more ideas?

 

patching file .htaccess
Hunk #1 FAILED at 184.
1 out of 1 hunk FAILED -- saving rejects to file .htaccess.rej
patching file .htaccess.sample

 

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

I have copied the content from the original htaccess and applied the patch again (4th time), it seems everything worked out but there are no new functions on my backend (config/admin/security) Smiley Sad which means the patch was not applied... last solution I'm thinking of is editing the content from the patch deleting lines in relation with the htaccess as explained here although I don't like to do that.... http://www.atwix.com/magento/security-patch-supee-6788-installation-issues/

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

Ugh, sounds like the patch apply from hell... I can give you a list of all the files that are patched. They should have the file date of the day you successfully applied the patch and should be listed in app/etc/applied.patches.list

A sampling of the dates on 6-8 files should tell you if there was any activity towards having the patch run.

 

If it dies on one file, it applies nothing at all. It's purposefully an all or nothing operation so it will not leave you in a half-dead state. Given the way this particular one works (SUPEE-6788), one of the security issues is cross-module and a partial apply will leave your site a heap of rubble.

 

As to application, this patch must be applied with the Magento cache fully disabled, cleared and the compiler shut off. People have had problems where they didn't do one or the other of the above and the table installer scripts fail to create the whitelist tables, even though they record the successful run of the installer scripts. Also, after you install, log into admin, log out and then back in to make sure the menu items actually load. Sounds like it's not a first time admin backend load missing menu items though.

You might prod Magentary to see if they will do the patch bundle for 1.6.2.0 which would reduce it to a simple file upload instead of a patch run.

.htaccess
.htaccess.sample
app/code/core/Mage/Admin/Model/Block.php
app/code/core/Mage/Admin/Model/Resource/Block.php
app/code/core/Mage/Admin/Model/Resource/Block/Collection.php
app/code/core/Mage/Admin/Model/Resource/Variable.php
app/code/core/Mage/Admin/Model/Resource/Variable/Collection.php
app/code/core/Mage/Admin/Model/Variable.php
app/code/core/Mage/Admin/etc/config.xml
app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.0-1.6.1.1.php
app/code/core/Mage/Admin/sql/admin_setup/upgrade-1.6.1.1-1.6.1.2.php
app/code/core/Mage/Adminhtml/Block/Permissions/Block.php
app/code/core/Mage/Adminhtml/Block/Permissions/Block/Edit.php
app/code/core/Mage/Adminhtml/Block/Permissions/Block/Edit/Form.php
app/code/core/Mage/Adminhtml/Block/Permissions/Block/Grid.php
app/code/core/Mage/Adminhtml/Block/Permissions/Variable.php
app/code/core/Mage/Adminhtml/Block/Permissions/Variable/Edit.php
app/code/core/Mage/Adminhtml/Block/Permissions/Variable/Edit/Form.php
app/code/core/Mage/Adminhtml/Block/Permissions/Variable/Grid.php
app/code/core/Mage/Adminhtml/controllers/Permissions/BlockController.php
app/code/core/Mage/Adminhtml/controllers/Permissions/VariableController.php
app/code/core/Mage/Adminhtml/etc/adminhtml.xml
app/code/core/Mage/Catalog/Model/Product/Option/Type/File.php
app/code/core/Mage/Core/Controller/Request/Http.php
app/code/core/Mage/Core/Controller/Varien/Router/Admin.php
app/code/core/Mage/Core/Helper/UnserializeArray.php
app/code/core/Mage/Core/Model/Email/Template/Filter.php
app/code/core/Mage/Core/Model/Resource/Setup.php
app/code/core/Mage/Core/etc/config.xml
app/code/core/Mage/Core/etc/system.xml
app/code/core/Mage/Customer/Block/Account/Changeforgotten.php
app/code/core/Mage/Customer/Block/Account/Resetpassword.php
app/code/core/Mage/Customer/controllers/AccountController.php
app/code/core/Mage/Downloadable/Model/Product/Type.php
app/code/core/Mage/Eav/Model/Resource/Attribute/Collection.php
app/code/core/Mage/Sales/Model/Resource/Order/Item/Collection.php
app/code/core/Mage/Sales/controllers/DownloadController.php
app/code/core/Zend/Soap/Server.php
app/code/core/Zend/Xml/Exception.php
app/code/core/Zend/Xml/Security.php
app/code/core/Zend/XmlRpc/Request.php
app/code/core/Zend/XmlRpc/Response.php
app/design/adminhtml/default/default/layout/admin.xml
app/design/frontend/base/default/layout/customer.xml
app/design/frontend/base/default/template/customer/form/register.phtml
app/design/frontend/base/default/template/customer/form/resetforgottenpassword.phtml
app/design/frontend/base/default/template/page/js/cookie.phtml
app/design/frontend/base/default/template/persistent/customer/form/register.phtml
errors/processor.php
lib/Unserialize/Parser.php
lib/Unserialize/Reader/Arr.php
lib/Unserialize/Reader/ArrKey.php
lib/Unserialize/Reader/ArrValue.php
lib/Unserialize/Reader/Bool.php
lib/Unserialize/Reader/Dbl.php
lib/Unserialize/Reader/Int.php
lib/Unserialize/Reader/Str.php
lib/Varien/Data/Collection/Db.php

Been dealing with module testing on staging all day to make sure nothing's busted before I consign myself to hell.

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

Hi Chiefair, @chiefair

 

Before editing the patch I would like to double check that all previous patches have been applied...

 

According to the applied.patches.list file the folllowing have been applied:

 

2015-02-24 18:21:47 UTC | SUPEE-2630 | EE_1.11.1.0 | v1 

2015-05-14 18:53:42 UTC | SUPEE-1533 | EE_1.11 | v1 

2015-05-14 18:53:53 UTC | SUPEE-2677 | EE_1.13.0.2 | v2 

2015-05-14 18:54:01 UTC | SUPEE-5346 | EE_1.11.1.0 | v1 

2015-05-15 16:16:28 UTC | SUPEE-5998 | EE_1.14.1.0 | v1 

2015-07-08 16:25:32 UTC | SUPEE-6285 | CE_1.6.2.0 | v1 

2015-08-31 09:00:16 UTC | SUPEE-6482 | CE_1.6.2.0 | v1 

 

Are you missing any of them?

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

Two were function enhancements (noted), the rest are security patches

 

2014-09 | SUPEE-2677 | EE_1.13.0.2 | v2 |
2014-09 | SUPEE-2725 |            | v1 |  <= Discovercard Patch
2014-09 | SUPEE-1868 | CE_1.7.0.2 | v1 |  <= USPS Ship Method
2014-09 | SUPEE-2630 | EE_1.11.1.0 | v1 |
2015-02 | SUPEE-1533 | EE_1.11 | v1 | _ |
2015-02 | SUPEE-5346 | EE_1.11.1.0 | v1 |
2015-05 | SUPEE-5998 | EE_1.14.1.0 | v1 |
2015-07 | SUPEE-6285 | CE_1.6.2.0 | v1 |
2015-08 | SUPEE-6482 | CE_1.6.2.0 | v1 |
2015-11 | SUPEE-6788 | CE_1.6.2.0 | v1 |

Re: 1.6.2.0 is getting the wrong SUPEE-6788 Version on download.

@chiefair 

 

The only ones I'm missing are the function enhancements that I assume they're not needed, so the only solution left is to edit the patch file . . .