Yeah, we started running into issues with an integration of one of our customers. We don’t typically use the Dynamics 365 Integration plugin, so it’s really not something I’m too familiar with. In fact, it was our customer who setup the integration. The way they’re using it is on a Gravity Form using the Dynamics 365 Plugin feed to submit data into their system.
After the WP Rocket update, the Dynamics 365 Plugin was no longer able to connect. The primary area we were seeing the issue was in the Dynamics 365 settings, it was showing “Not Connected” and after entering credentials and pressing the “Connect” button it would throw a fatal error. Here’s what we were able to pull from the logs. Note these logs are truncated and slightly modified to protect customer privacy and data structure. I can attempt to get the full stack trace if necessary, but it might take some time.
An error of type E_ERROR was caused in line 194 of the file wp-content/plugins/integration-dynamics/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php. Error message: Uncaught Error: Undefined class constant ‘Monolog\Utils::DEFAULT_JSON_FLAGS’ in wp-content/plugins/integration-dynamics/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php:194
Stack trace:
#0 wp-content/plugins/integration-dynamics/vendor/monolog/monolog/src/Monolog/Handler/AbstractHandler.php(113): Monolog\Handler\AbstractHandler->getDefaultFormatter()
#1 wp-content/plugins/integration-dynamics/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php(37): Monolog\Handler\AbstractHandler->getFormatter()
#2 wp-content/plugins/integration-dynamics/vendor/monolog/monolog/src/Monolog/Logger.php(344): Monolog\Handler\AbstractProcessingHandler->handle()
#3 wp-content/plugins/integration-dynamics/vendor/monolog/monolog/src/Monolog/Logger.php(754): Monolog\Logger->addRecord()
#4 wp-content/plugins/integration-dynamics/src/Connection
For the time being, we rolled WP Rocket back to to version 3.11.5, which was the release prior to the Monolog upgrade.