You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
You're running version >=1.0.23 of Parse Dashboard.
You're running version >=2.3.2 of Parse Server.
You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
PostgreSQL 10.13
Parse Server 3.2.0 (installed over npm)
Parse Dashboard 2.1.0 (installed over npm)
Steps to reproduce
Add new row to one of existing classes manually over the parse dashboard.
2. Reload the page. After reload all counters are showing zero, but there are rows inside.
The same behavior in Safari and Chrome.
Logs/Trace
Note: If you get a browser JS error please run npm run dev. This will provide source maps and a much more useful stack trace.
There are now errors in the log file and no JS errors in the browser.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
You're running version >=1.0.23 of Parse Dashboard.
You're running version >=2.3.2 of Parse Server.
You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
PostgreSQL 10.13
Parse Server 3.2.0 (installed over npm)
Parse Dashboard 2.1.0 (installed over npm)
Steps to reproduce
2. Reload the page. After reload all counters are showing zero, but there are rows inside.
The same behavior in Safari and Chrome.
Logs/Trace
Note: If you get a browser JS error please run
npm run dev
. This will provide source maps and a much more useful stack trace.There are now errors in the log file and no JS errors in the browser.
The text was updated successfully, but these errors were encountered: