Skip to content

Opening the filter menu in data browser throws an error #1915

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

Closed
4 tasks done
mtrezza opened this issue Nov 2, 2021 · 5 comments
Closed
4 tasks done

Opening the filter menu in data browser throws an error #1915

mtrezza opened this issue Nov 2, 2021 · 5 comments
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@mtrezza
Copy link
Member

mtrezza commented Nov 2, 2021

New Issue Checklist

Issue Description

Opening the filter menu in data browser throws an error:

TypeError: undefined is not an object (evaluating 't.currentApp.columnPreference[s]')

The page becomes blank.

Steps to reproduce

  1. open dashboard
  2. open data browser
  3. click on "Filter" menu

Actual Outcome

page becomes blank

Expected Outcome

filter menu should be displayed

Environment

Dashboard

  • Parse Dashboard version: 3.3.0-alpha.15
  • Browser (Safari, Chrome, Firefox, Edge, etc.): Safari

Logs

n/a

@parse-github-assistant
Copy link

parse-github-assistant bot commented Nov 2, 2021

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added bounty:$10 Bounty applies for fixing this issue (Parse Bounty Program) severity:high type:bug Impaired feature or lacking behavior that is likely assumed labels Nov 2, 2021
@mtrezza
Copy link
Member Author

mtrezza commented Nov 2, 2021

Bug also exists in beta, needs to be ported

@mtrezza mtrezza closed this as completed Nov 2, 2021
@mtrezza mtrezza reopened this Nov 2, 2021
@mtrezza mtrezza added bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) and removed bounty:$10 Bounty applies for fixing this issue (Parse Bounty Program) labels Nov 6, 2021
@sadortun
Copy link

sadortun commented Feb 5, 2022

@mtrezza Chan you cherry-pick #1958 into 3.3.x patch ?

@mtrezza
Copy link
Member Author

mtrezza commented Feb 6, 2022

We only cherry-pick vulnerability fixes, due to the required effort. It was a small fix, so I think you could just add it to your fork until you upgrade to an official release that includes the fix.

@mtrezza
Copy link
Member Author

mtrezza commented Feb 6, 2022

Closing via #1958

@mtrezza mtrezza closed this as completed Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

2 participants