If you have SSH access, it would be more simple to apply the patch via SSH.
If you have no SSH access to apply the patch, you can simply upgrade your installation to Magento 126.96.36.199 version which includes all the latest security patches (SUPEE-5344,SUPEE-5994,SUPEE-6285,SUPEE-6482,SUPEE-6788,SUPEE-7405,SUPEE-8788, SUPEE-9652,SUPEE-9767). If Magento upgrade is not possible in the moment due to some reason you still can apply the patch via FTP/sFTP upload as shown in this article.
If you wish to save time and have us to install these patches for you, simply click here to order installation.
- Disable Magento Compiler is an operation performed before every code change like installation of Magento Connect extensions, Magento upgrade or manual changes in code files.
Magento Compiler is a plain PHP class used to combine PHP class definitions into files under
includes/src/directory. At this time, in most cases this is obsoleted by native PHP opcode caches such as APC, xCache, eAccelerator, Zend Opcache, ionCube Accelerator and so on, you can find the list of opcode caches here. So, if you have opcode cache loaded, do not use Magento Compiler as it is useless and will just cause troubles on every code modification.
To disable Magento Compiler in Backend you can navigate to System > Tools > Compilation and click on Flush cache button.
- If shell/SSH console is not possible in your case, you still can disable Magento compiler via FTP or any FileManager. You just need to move
includes/directory out (renaming or deleting it) and create a new empty
includes/directory with empty
includes/config.phpfile inside if you wish to enable Magento Compiler again some day, otherwise it will complain that can not find that directory.” class=”glossaryLink “>Disable Magento Compiler and clear compiler cache
Applying Magento patches via FTP/sFTP or FileManager / File Upload
To apply patches in this way we simply replace changed files. This way can not be used blindly if you or your developers have changed any core Magento files. Such changes should be re-applied to patched files, or you loose these changes.
Note: To the moment, the patch have no any dependencies and can be installed any time with any set of installed patches or without any patches.
The following file is changed by SUPEE-8167 is a small compatibility patch with new PayPal IPN server location. It is required to keep PayPal processing transactions past June 30, 2017.” class=”glossaryLink “>SUPEE-8167:
To install the patch via FTP/File Upload
- select patch bundle archive corresponding to your Magento version from the table below and unpack it
- upload all files and folders to Magento root directory of your store, replacing all files
Downloads for other versions added to table on demand when we patch certain version via file upload for the first time.
Check if your cURL PHP library have TLS1.2
PayPal switching to TLS1.2 only on June 30, so it is important to verify that your Magento still will be able to connect to PayPal. Navigate to PayPal payment settings page in Backend and check if you have warnings as described in
Verification and flush of Magento PHP opcode cache
Flush Magento cache: Navigate in Magento backend to System > Cache Management and click on Flush cache button.
If you use PHP opcode caches (OPCache/APC/XCache/eAccelerator) make sure to flush it after patching (or restart webserver), otherwise code will continue to run from caches.
Test that your store is working.