Our Solution For Magento Logging Failed After Installing SUPEE 11086 Patch
Magento SUPEE 11086 was released on March 26, 2019. The patch is meant to fix issues like close remote code execution (RCE), cross-site scripting (XSS), cross-site request forgery (CSRF) and other vulnerabilities.
However, it comes with an issue of Magento Logging Failed After Installing SUPEE 11086 Patch!
The problem is caused due to the log validation function added by Magento to validate extensions. It throws an error on is_readable() function in the case log file does not exist yet.
Implement the below solution to overcome the Magento Logging issue.
Solution for Magento Logging Failed After Installing SUPEE 11086 Patch:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
$logValidator = new Zend_Validate_File_Extension($_allowedFileExtensions); $logDir = self::getBaseDir('var') . DS . 'log'; if (!$logValidator->isValid($logDir . DS . $file)) { return; } replace with // $logValidator = new Zend_Validate_File_Extension($_allowedFileExtensions); $logDir = self::getBaseDir('var') . DS . 'log'; //if (!$logValidator->isValid($logDir . DS . $file)) { // return; //} |
Note: However, with the release of Magento SUPEE 11155, this issue is resolved and you don’t need to implement the above solution.
Please let me know if you still face any issue with Magento logging after the SUPEE Patch 11086 installation.
I’d be happy to help 🙂
Thanks!
Sanjay Jethva
Sanjay is the co-founder and CTO of Meetanshi with hands-on expertise with Magento since 2011. He specializes in complex development, integrations, extensions, and customizations. Sanjay is one the top 50 contributor to the Magento community and is recognized by Adobe.
His passion for Magento 2 and Shopify solutions has made him a trusted source for businesses seeking to optimize their online stores. He loves sharing technical solutions related to Magento 2 & Shopify.
2 Comments
This fix breaks SUPEE-11155 (June M1 security patch). Be sure to put the original file back before upgrading to 1.9.4.2 or your upgrade patch will fail.
Yes, you are correct.
This is just a temporary workaround until its fixed.
Thank you for the heads up 🙂