Closed c-w closed 6 years ago
Hypothesis:
Setting bbox to a default dummy value like [0,0,0,0]
will fix the issue while doing no harm since the user is required to configure their bounding box of interest anyways after the deployment.
Evidence:
Further evidence:
After this change:
diff --git a/src/actions/Dashboard/index.js b/src/actions/Dashboard/index.js
index 34b8451..75cb36a 100644
--- a/src/actions/Dashboard/index.js
+++ b/src/actions/Dashboard/index.js
@@ -27,6 +27,8 @@ function fetchCommonTerms(settings, callback, timespanType, fromDate, toDate, ca
configuration = configuration && configuration.site && configuration.site.properties;
const dataSources = toDataSources((streams && streams.streams) || []);
+ if (!configuration.targetBbox) configuration.targetBbox = [0, 0, 0, 0];
+
DashboardServices.getCommonTerms(timespanType, fromDate, toDate, configuration.targetBbox, configuration.defaultZoomLevel, category,
(error, response, body) => ResponseHandler(error, response, body, (err, topics) => {
if (!err) {
The admin page now loads:
Fix worked and was deployed succesfuly via ARM:
After a successful deployment:
The admin page gives an error:
The error is thrown here:
Error response:
This happens after an earlier request to the settings endpoint that returned: