Changed the log level on exceptions in BlockRenderer from critical to…

… error (#285)

As critical, log entries may trigger further actions, i.e. sending mails from monolog and similar. This makes even more sense as the default settings in the block bundle simply catch the exception.

Block/BlockRenderer.php

@@ -93,7 +93,11 @@ public function render(BlockContextInterface $blockContext, Response $response =
             $response = $this->addMetaInformation($response, $blockContext, $service);
         } catch (\Exception $exception) {
             if ($this->logger) {
-                $this->logger->critical(sprintf('[cms::renderBlock] block.id=%d - error while rendering block - %s', $block->getId(), $exception->getMessage()));
+                $this->logger->error(sprintf(
+                    '[cms::renderBlock] block.id=%d - error while rendering block - %s',
+                    $block->getId(),
+                    $exception->getMessage()
+                ), compact('exception'));
             }
 
             // reseting the state object

Tests/Block/BlockRendererTest.php

@@ -104,7 +104,7 @@ public function testRenderWithWrongResponse()
             }));
 
         // mock the logger to ensure a crit message is logged
-        $this->logger->expects($this->once())->method('critical');
+        $this->logger->expects($this->once())->method('error');
 
         // mock a block object
         $block = $this->getMock('Sonata\BlockBundle\Model\BlockInterface');
@@ -145,7 +145,7 @@ public function testRenderBlockWithException()
             ->will($this->returnValue($response));
 
         // mock the logger to ensure a crit message is logged
-        $this->logger->expects($this->once())->method('critical');
+        $this->logger->expects($this->once())->method('error');
 
         // mock a block object
         $block = $this->getMock('Sonata\BlockBundle\Model\BlockInterface');