search

socialappslab / denguechat

Using mobile phones and gaming tactics to engage citizens in reporting public health risks
https://www.denguechat.org/
Other
0 stars 0 forks source link

The map in DengueChat Datos is not displaying any points and shows error messages #963

Closed cdparra closed 3 years ago

cdparra commented 3 years ago

Below is a picture that shows how the problems manifests

image

These are the errors showing up in the console: 

Failed to load resource: the server responded with a status of 404 (Not Found)
map-icons.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:12594 TypeError: Cannot read property 'DataTable' of undefined
    at drawChart (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:38189)
    at application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:38115
    at processQueue (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:14866)
    at application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:14882
    at Scope.$eval (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:16126)
    at Scope.$digest (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:15944)
    at Scope.$apply (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:16234)
    at done (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:10663)
    at completeRequest (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:10861)
    at XMLHttpRequest.requestLoaded (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:10802)
(anonymous) @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:12594
(anonymous) @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:9366
processQueue @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:14874
(anonymous) @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:14882
$eval @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:16126
$digest @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:15944
$apply @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:16234
done @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:10663
completeRequest @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:10861
requestLoaded @ application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:10802
application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:12594 ReferenceError: MarkerClusterer is not defined
    at Object.<anonymous> (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:38299)
    at Object.invoke (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:4597)
    at extend.instance (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:9256)
    at nodeLinkFn (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:8373)
    at compositeLinkFn (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:7805)
    at compositeLinkFn (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:7808)
    at publicLinkFn (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:7685)
    at boundTranscludeFn (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:7823)
    at controllersBoundTransclude (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:8436)
    at Object.ngIfWatchAction [as fn] (application-ecab2722943c88f1e6b75334530a2abf4615a7f35be5714d03cfa9fbbc29e75b.js:24200)

Investigate why is this happenning (might be an issue with Google API having updated and changed in ways that our current implementation does not use properly)