What to do:
If you’re using with custom versions of those templates you’ll have to update them by adding the following code into them:
php echo $this->getBlockHtml('formkey') ?>
If you’re using a 3rd party checkout module, you’ll have to get in touch with them so they can provide an updated version of their module.
Also if you have custom versions of the previously listed JS files, you’ll have to update them too.
SAVE YOUR TIME:
Fabian Schmengler wrote a nice little script to update all those things for you, you can find it here:
The checkout form key validation can be changed in the backend via a new config field under System > Configuration > Admin > Security > Enable Form Key Validation On Checkout . THIS IS NOT ENABLED BY DEFAULT so you’ll have to enable it to benefit from this security feature! Note that you’ll get a notice in the backend if it’s not enabled.
Image Upload callback
The image gallery controller has been updated to add a validation callback.
What to do
If you’re using a custom module that does image upload with code that looks like this:
$uploader = new Mage_Core_Model_File_Uploader('image');
I strongly suggest you update that code by adding the following piece after it:
Security patch SUPEE-9767 removes the system configuration field that allows you to allow template symlinks in the backend. It used to be under System > Configuration > Developer > Template > Allow Symlinks . Now the entire Template section is gone.
On top of that, that field is now disabled by default via the
The funny thing here is that you’ll get a notice in the backend if you have that configuration field enabled prior to the patch but you won’t be able to disable it as the field is gone.
Only way of doing it is by running the following SQL query
UPDATE core_config_data SET value = 0 WHERE path = "dev/template/allow_symlink";
First, we strongly suggest you check posts that will help you understand the purpose of that Symlink modification (a simple Google search about this would suffice):
What to do: if you’re using modman or composer with template symlinks, you’re gonna face some issues. I’m still trying to find out what’s the best thing to do here apart from dealing with SQL queries.
List of other possible issues with Security Patch SUPEE-9767
Hunk Failed Issues
Note that all those issues could be simply because you modified the original file, to double check that this is not the case:
- Backup the file where you get the Hunk Failed error
- Download the original file from your Magento version
- Compare both files
If files are different you’ll have to apply security patch SUPEE-9767 with the original file then reapply your custom changes the clean way such as:
- custom template in a custom theme folder
- app/code/local file
If files are not different then this is either a permission issue or a “bug” in the patch.