Skip to content
New issue

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

When some columns are invisible I can not edit visible column values #1362

Closed
suathh opened this issue Oct 31, 2019 · 4 comments
Closed

When some columns are invisible I can not edit visible column values #1362

suathh opened this issue Oct 31, 2019 · 4 comments
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@suathh
Copy link

suathh commented Oct 31, 2019

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

  • [ X] You're running version >=1.0.23 of Parse Dashboard.

  • [ X] You're running version >=2.3.2 of Parse Server.

  • [ X] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

"dependencies": {
"csv": "^5.1.2",
"csvtojson": "^2.0.10",
"express": "~4.11.x",
"kerberos": "~0.0.x",
"parse": "~1.8.0",
"parse-server": "*"
},
"scripts": {
"start": "node index.js"
},
"engines": {
"node": ">=4.3"
}

Steps to reproduce

Use Manage Columns and hide any column and try to change value of any visible column

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.

@davimacedo davimacedo added the type:bug Impaired feature or lacking behavior that is likely assumed label Nov 11, 2019
@Simone-cogno
Copy link

Simone-cogno commented Nov 20, 2019

Any plan to fix this? The function of hiding columns is very useful but cannot be used anymore (you should disabled all the hided columns every time you want to modify one field)

@davimacedo
Copy link
Member

@suathh I was looking at this issue and not able to reproduce anymore. Could you please confirm if that's still happening or not?

@suathh
Copy link
Author

suathh commented Jun 4, 2021

@davimacedo I tried with couple of different instances and I can say that problem is not persist anymore

@mtrezza
Copy link
Member

mtrezza commented Jun 4, 2021

@suathh thanks for reporting back, closing this issue.

@mtrezza mtrezza closed this as completed Jun 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

4 participants