Installing Patches with SSH

Whenever a patch is released to fix an issue in the code, a notice is sent directly to your Admin
InboxInbox. If the update is security related, the incoming message is color-coded red, and
marked as a “Critical Update.”
Make sure to stop by our Magento Security Center, and sign up for the Security Alert Registry to
receive direct notification from our security team of any emerging issues and solutions.
The following instructions explain how to download and install a patch, starting with a notice
that appears in your Admin Inbox. The example takes place on a Windows system, and uses
the WinSCP utility to upload patch files to the server, and Putty to access the server from the
command line. You can download both utilities at no charge. If you are a Mac user, you can
access the command line with Terminal.
If this is the first time you have installed a patch, we recommend that you complete the
optional steps to create a backup copy of your store and install a patch as a test run. If you
have experience installing patches, you can take the fast track and skip the optional steps. For
advanced instructions, see the following articles in the Magento developer documentation: 
How to Apply and Revert Magento Patches
Recommended File System Ownership and Privileges

Before you begin…

To install a patch, you must have a user name and password to access the server. In addition
to your own login credentials, you might also need the apache password. If you don’t have
these credentials, contact the person who set up your server.

Process Overview:
Step 1:   Download the Patch
Step 2:   Set the Necessary Permissions
Step 3:   Create a Backup of the Magento Folder (Optional)
Step 4:   Upload the Patch
Step 5:   Install the Patch on the Backup (Optional)
Step 6:   Install the Patch to Your Store
Step 7:   A Little Housekeeping (Optional)
Step 8:   Look for Signs of Unauthorized Access (For security-related issues)
Step 9:   Clear the Magento Cache
Step 10: Recompile the Store (Only if compiled)
Step 11: Restart the Server

Leave a Comment

Your email address will not be published. Required fields are marked *