[Fixed] Magento Logging Failed After Installing SUPEE 11086 Patch

Moreover, have you faced an issue of Magento logging failed after installing SUPEE 11086 patch? This is because 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. To solve this problem, check here.

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:

The below screenshot shows how I have implemented the solution:

[Fixed] Magento Custom Logging Failed After Installing SUPEE 11086 Patch

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!

5
(based on 4 Reviews)

Sanjay is a co-founder at Meetanshi. He is a certified Magento developer who loves creating Magento E-commerce solutions. When he is not engrossed with anything related to Magento, he loves to play cricket.

2 comments On [Fixed] Magento Logging Failed After Installing SUPEE 11086 Patch

  • 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 🙂

Leave a Reply