Fix legacy mapper exceptions when there is no database (#79)

ezsystems · Feb 10, 2017 · 7f6b0aa · 7f6b0aa
1 parent 09ac6da
commit 7f6b0aa
Showing 1 changed file with 11 additions and 1 deletion.
diff --git a/bundle/LegacyMapper/Configuration.php b/bundle/LegacyMapper/Configuration.php
@@ -21,6 +21,7 @@
 use Symfony\Component\DependencyInjection\ContainerAwareTrait;
 use Symfony\Component\EventDispatcher\EventSubscriberInterface;
 use RuntimeException;
+use Exception;
 
 /**
  * Maps configuration parameters to the legacy parameters.
@@ -281,7 +282,16 @@ private function getMultiSiteSettings()
             return $result;
         }
 
-        $pathPrefix = trim($this->urlAliasGenerator->getPathPrefixByRootLocationId($rootLocationId), '/');
+        $pathPrefix = '';
+
+        try {
+            $pathPrefix = trim($this->urlAliasGenerator->getPathPrefixByRootLocationId($rootLocationId), '/');
+        } catch (Exception $e) {
+            // Ignore any errors
+            // Most probable cause for error is database not being ready yet,
+            // i.e. initial install of the project which includes eZ Publish Legacy
+        }
+
         $pathPrefixExcludeItems = array_map(
             function ($value) {
                 return trim($value, '/');