- Dropped sessions issue (with fix) (http://magento.stackexchange.com/a/116324/2380https://magento.stackexchange.com/a/116324/2380)
- Unable to login to the backend after the patch: "Invalid form key" error. => Flush your browser cookies and delete the var/session files (Magento 1.9.2.3. not login in google chromeMagento 1.9.2.3. not login in google chrome)
- (fixed in v1.1 of the patch)
Admin order view page is blank / broken => Related to the PHP < 5.4 incompatibility. => Fix can be found here: http://magento.stackexchange.com/a/98237/2380https://magento.stackexchange.com/a/98237/2380 / I've created a bug report: https://www.magentocommerce.com/bug-tracking/issue/index/id/1266 (credits: @Moonman67). - (fixed in v1.1 of the patch)
SOAP API URL/index.php/api/v2_soap/index/?wsdl=1throws a 500 error => I've developped a hacky fix for this one that can be found here: http://magento.stackexchange.com/a/98790/2380https://magento.stackexchange.com/a/98790/2380 / I've also created a bug report for this one: https://www.magentocommerce.com/bug-tracking/issue/index/id/1265 (credits: @Moonman67) - (fixed in v1.1 of the patch)
Issues regarding file upload permissions - Applying patch on Magento 1.7.0.0 breaks: http://magento.stackexchange.com/a/98246/2380https://magento.stackexchange.com/a/98246/2380
- Checkout not redirecting to success page on HHVM: http://magento.stackexchange.com/a/98334/2380https://magento.stackexchange.com/a/98334/2380
- Undefined class constant AREA ADMINHTML in
app/code/core/Mage/Core/Model/Config.php(possibly EE only): SUPEE 7405 Enterprise Edition Fatal error Undefined class constant 'AREA_ADMINHTMLSUPEE 7405 Enterprise Edition Fatal error Undefined class constant 'AREA_ADMINHTML - Call to undefined method
Mage_Core_Helper_Abstract::escapeHtml()on 1.4.0.1 : Error after installing patch 7405 on Magento 1.4.0.1Error after installing patch 7405 on Magento 1.4.0.1 - Mage registry key
_singleton/Mage_Core_Model_Domainpolicyalready exists on Magento 1.7: Security Patch SUPEE-7405 ErrorSecurity Patch SUPEE-7405 Error - Call to a member function getUsername() on a non-object after the patch: Magento Admin thrown error after applying SUPEE 7405 security patchMagento Admin thrown error after applying SUPEE 7405 security patch
- Unable to add permission block after patch on 1.8.1.0 : After Security patch supee-7405 topmenu is not displayingAfter Security patch supee-7405 topmenu is not displaying
- (Previous patch not applied)
Issues applying the patch on 1.7.0.2 : Security Patch SUPEE-7405 IssuesSecurity Patch SUPEE-7405 Issues - (Core files had been changed)
Issues applying the patch on 1.8.1 : supee 7405 Hunk #2 FAILED at 472. Magento 1.8.1supee 7405 Hunk #2 FAILED at 472. Magento 1.8.1 - (Provider related)
Email queue broken after patch : Magento 1.9.2.3 Email-Queue not working
It can be found on this page here: http://magento.stackexchange.com/a/98232/2380https://magento.stackexchange.com/a/98232/2380 (credits @MagenX)
- If you updated from Magento EE 1.14.2.x to Magento EE 1.14.2.3 instead of applying the patch, and also applied the support patch SUPEE-5984 before, you have to reapply it again because it is not included in the release. => http://magento.stackexchange.com/a/98805/2380https://magento.stackexchange.com/a/98805/2380
- Seems like patches 4291 and 6237 need to be applied before applying the patch. More information here: Apply 7616_EE 7405_EE patch not successfulyApply 7616_EE 7405_EE patch not successfuly
- (Patch 5344 had not been applied)
Possible problem when applying 7616 before applying 7405: SUPEE 7405 - Hunk #2 Failed at 43SUPEE 7405 - Hunk #2 Failed at 43
- Critical Reminder: Download and install Magento security patches. (FTP with no SSH access)Critical Reminder: Download and install Magento security patches. (FTP with no SSH access)
- Mage Report has added a check for SUPEE-7405: https://www.magereport.com/
