cancel
Showing results for 
Search instead for 
Did you mean: 

Magento 1.6 - SUPEE-6788

SOLVED

Re: Magento 1.6 - SUPEE-6788

One highly informative line from the patch that indicates it's totally wrong for 1.6.2.0 is this:

 

--- dev/tests/functional/.htaccess

 

The dev/tests/ directory structure is introduced in Magento CE 1.9

Re: Magento 1.6 - SUPEE-6788

The download option for 1.6.2.0 appears to still be downloading the 1.9.2.0 patch. Frankly I'm a little disappointed.

Re: Magento 1.6 - SUPEE-6788

When are they going to upload the correct file?

 

Re: Magento 1.6 - SUPEE-6788

Hi Guys,

 

It seems that the proper file for 1.6.2 has been finally added.

 

bEST,

Re: Magento 1.6 - SUPEE-6788

Sorry for the delay, and error, everyone. The corrected version is uploaded for 1.6.2.0 now.

--

Developer Relations, Adobe Experience Cloud
Problem solved? Click Accept as Solution!
Still stuck? Check out our documentation: https://magento.com/resources/technical

Re: Magento 1.6 - SUPEE-6788

I'm afraid it's not fully compatible with a Magento v1.6.2. already patched... before installing please check that topic https://community.magento.com/t5/Security-Patches/1-6-2-0-is-getting-the-wrong-SUPEE-6788-Version-on...

Re: Magento 1.6 - SUPEE-6788

@baghulia

 

Except in a special instance of a backport for SUPEE-6482, the file mentioned in the other thread should not be an issue for you.

 

What will hang you up is if you have a modified .htaccess (who doesn't) which means save a copy, snag the stock version from the 1.6.2.0 install archive and also replace .htaccess.sample if you removed it to clean up the directory contents.

Re: Magento 1.6 - SUPEE-6788

Hi, thanks I'll back it up (.htc) prior to patch application...

Re: Magento 1.6 - SUPEE-6788

Just wanna make a note on here even though this post is a little old now.

 

I just applied the 6788 patch to a client's 1.6.0.0 Magento install and it turns out the patch was expecting the admin_setup entry in the core_resource table to be 1.6.0.0.1.1 but instead it was actually 1.6.1.0 so the patch "applied successfully" in SSH but threw exception errors in the admin cause it didn't create the permission_block and permission_variable tables in the database.

 

I simply followed the instructions in the post that was marked as the solution but instead put 1.6.0.0.1.1 in the database to match line 629 of the patch and it finally worked fine. Yes, I want to update this site to a more current version of Magento but I don't have a say so in that sadly. Smiley Sad

 

Hope this helps someone. 

Re: Magento 1.6 - SUPEE-6788

Glad you were able to get that sorted @epeets, thanks for sharing so that your findings can help someone else!

--

Developer Relations, Adobe Experience Cloud
Problem solved? Click Accept as Solution!
Still stuck? Check out our documentation: https://magento.com/resources/technical