• Resolved jeffersonpowers

    (@jeffersonpowers)


    I received one of those “your site is experiencing a technical issue” emails today. The website was completely crashed, but I was able to log in via recovery mode, and discovered that Shield Security (the current version, 16.1.9) was causing the following error:

    An error of type E_COMPILE_ERROR was caused in line 26 of the file /var/www/wp-content/plugins/wp-simple-firewall/src/lib/src/Modules/AuditTrail/Lib/LogHandlers/LocalDbWriter.php. Error message: Declaration of FernleafSystems\Wordpress\Plugin\Shield\Modules\AuditTrail\Lib\LogHandlers\LocalDbWriter::write(array $record) must be compatible with Monolog\Handler\AbstractProcessingHandler::write(array $record): void

    Deactivating Shield restored the website. I did some further testing and figured out that the problem appears to be an incompatibility with the WP-Optimize plugin version 3.2.9 (this issue came up after an automatic update of WP-Optimize). Deactivating either plugin fixes the issue.

    I can say for sure that this problem doesn’t exist with WP_Optimize version 3.2.7 (I’m not sure about 3.2.8), so it’s something to do with a recent change to WP-Optimize. However, it does appear to be Shield Security that is generating the error.

Viewing 1 replies (of 1 total)
  • Plugin Author Paul

    (@paultgoodchild)

    It appears to be Shield generating the error, but as you’ve discovered, it’s both plugins together causing the problem. We each have a different, incompatible, version of the PHP monolog library distributed with our plugin. Our plugin throws the error just by the timing of the included library.

    We include a version of the monolog library that is most widely compatible with more WordPress sites. WPOptimise has unfortunately chosen a version of the library (v2.3.5) that is only compatible with PHP 7.2+. This is strange since their plugin states PHP 5.6+ compatibility. You’ll want to ask them if they’d consider using an older version of the library.

Viewing 1 replies (of 1 total)
  • The topic ‘Critical incompatibility with WP-Optimize plugin’ is closed to new replies.