Error and warning on empty dashboard

[philippeluickx]

On nightly. Simply navigating to dashboard throws an error and a warning in console.
The text shows correctly on the page though:

You don't have any API Backend you manage.
To add an API Backend, click here.

4adc71e….js?meteor_js_resource=true:207 pathFor couldn't find a route named "addApiBackend-wizard"
4adc71e….js?meteor_js_resource=true:3 Exception in delivering result of invoking 'getElasticSearchData': TypeError: Cannot read property 'hits' of undefined
    at https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:393:14877
    at c._callback (https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:3:7449)
    at c._maybeInvokeCallback (https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:125:9141)
    at c.receiveResult (https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:125:9449)
    at o._livedata_result (https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:125:21537)
    at o (https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:125:6987)
    at https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:125:608
    at Array.forEach (native)
    at Function.A.each.A.forEach (https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:1:865)
    at r.t.socket.onmessage (https://nightly.apinf.io/4adc71e3c46d439cb6f8e80eeb5efd11b71cd0f0.js?meteor_js_resource=true:125:566)
4adc71e….js?meteor_js_resource=true:393 n {error: "No Living connections", reason: undefined, details: undefined, message: "[No Living connections]", errorType: "Meteor.Error"}

[bajiat]

@frenchbread Could you take a look at the error?

[frenchbread]

Related to #1643.

Since we deprecated addApiBackend-wizard, the pathFor value (the URL) has not been changed. Changing the href parameter value for <a> tag should resolve this.

[brylie]

Both of these errors have been fixed in separate PRs.

[brylie]

We have also fixed the text link for 'no results available' to be a button.

Closing.