We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
[Yes ] You're running version >=1.0.23 of Parse Dashboard.
[ Yes] You're running version >=2.3.2 of Parse Server.
[Yes ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.
The latest version of Parse Dashboard (2.0.1), and Parse and Parse-Server also are the latest. I upgrade them today.
Choose 1 or 2 rows, the option (Edit -> Delete these rows) is disabled.
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.
npm run dev
The text was updated successfully, but these errors were encountered:
This is a bug of last release that was already fixed here.
I've just prepared a new release here that will be published as soon as possible with the fix.
Sorry, something went wrong.
Thank you so much !
No branches or pull requests
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
[Yes ] You're running version >=1.0.23 of Parse Dashboard.
[ Yes] You're running version >=2.3.2 of Parse Server.
[Yes ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Environment Setup
The latest version of Parse Dashboard (2.0.1), and Parse and Parse-Server also are the latest. I upgrade them today.
Steps to reproduce
Choose 1 or 2 rows, the option (Edit -> Delete these rows) is disabled.
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.The text was updated successfully, but these errors were encountered: