Dashboard not working anymore!

2,192 views
Skip to first unread message

rob

unread,
Nov 15, 2014, 4:32:27 PM11/15/14
to fireba...@googlegroups.com
I keep on getting this message: 

Due to the number of records at this location the data viewer is in static viewing mode (non realtime, read only). Click on a key to see a realtime view.
    When I actually click into a record I am unable to edit it. I have removed all chrome extensions, restarted chrome and tried on canary. No dice. This service is almost useless if I can not live-edit records.

    Also, the chrome extension is basically useless. It continually just shows 'Loading...'

    Am I alone on these issues or is firebase having major problems? I am starting to rethink using firebase with my apps and that will require months of work to change things. The service simply isn't worth it if you can't live-edit records cleanly and I simply dont want to build my own editor... I mean...

Jacob Wenger

unread,
Nov 16, 2014, 3:25:47 PM11/16/14
to fireba...@googlegroups.com
Hey Rob,

Sorry you are having issues with Vulcan. The message you are seeing is not a bug, it is simply a result of the fact that you have a lot of data in your Firebase. If you have a lot of nodes in your Firebase (say thousands), we need to create a new <div> element for each node and modern browsers simply have limitations of how many DOM elements you can add to a page. We can download more data, but your browser will slow to a crawl before they are displayed. Instead of showing a loading spinner, we show a warning and give you data in "non-realtime" mode. To resolve this problem, don't load your Firebase Dashboard at the root of your Firebase, but instead load it lower down in the hierarchy. So (ignoring Vulcan for a second), say you are trying to load data at https://<your-firebase>.firebaseio.com and it gives you the "too much data" warning. If you go to https://<your-firebase>.firebaseio.com/messages instead, you might be able to see the data in "realtime mode." Better yet, you could go to https://<your-firebase>.firebaseio.com/messages/message151241 and certainly live edit that individual record. Again, this is most often a limitation of how many DOM elements a browser can display, not how much data Firebase can pull down to your browser (although that can also be a problem).

As for Vulcan, this is a project we are actively working to make better. If you feel like you have found a reproducible bug or have a feature request, please create a new issue in Vulcan's issue tracker on GitHub. Some discussion about your exact complaints are already ongoing.

If you still have issues, please reach out to us at sup...@firebase.com and we can give you some more personalized support. We can talk with you about how you are structuring your data and how much data you are storing to see if we can make things (including the Firebase Dashboard) more performant. 

Jacob

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages