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

Search queries not properly escaped. #6188

Closed
mixxxbot opened this issue Aug 22, 2022 · 8 comments
Closed

Search queries not properly escaped. #6188

mixxxbot opened this issue Aug 22, 2022 · 8 comments
Labels
bug duplicate This issue is a duplicate of or superseded by another issue.

Comments

@mixxxbot
Copy link
Collaborator

Reported by: mangelasakis
Date: 2011-12-17T18:57:35Z
Status: Fix Committed
Importance: Medium
Launchpad Issue: lp905776


Hi sorry for my English.
I have upgraded the mixxx at 1.9.2 amd64 and at 1.10 amd64 version at ubuntu 11.10 amd64 and when I search with 1A or 2A or 3A or 4A there are no results. But between 5A and 12A I have normaly results. The "1A ,5A, 6A... " is the key of the tracks.

The key details are in the file name and in the comments field too. With version 1.9.0 I had installed the ubuntu software center I had no problem ...The problem appeared after I upgraded from version 1.9.0 to version 1.9.2 and still exists in 1.10.

Rather it is a bug, because the same problem exists in debian amd64 and windows 7 x64.

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2011-12-17T19:15:32Z


Thanks for the informative report!

  • Do the tracks that you are looking for show up in the library table when you are not searching?

  • When you find them in the library, do you see the key (1A, 5A, etc.) in the comments field or in the location field? You could also check the track properties to make sure Mixxx has the key in the comment field.

  • What file type are they?

@mixxxbot mixxxbot added bug duplicate This issue is a duplicate of or superseded by another issue. labels Aug 22, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: mangelasakis
Date: 2011-12-18T17:41:29Z


yes the tracks show up in the library table and I can see the key in the location field (for examples /home/username/music/tiesto-traffic(original) - 3A) and in the comments field. When I search without a name and only with key from 1A to 4A(or 1B to 4B) , it doesn't show up the tracks. But when I search with others keys, they show up normaly... The type of files is mp3.

@mixxxbot
Copy link
Collaborator Author

Commented by: mangelasakis
Date: 2011-12-18T18:12:35Z


It shows up only the tracks who I have just played, but if I close the mixxx and I open it again and I search for the same track without I have played it again from the last time, it doesn't show up the track...

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2011-12-18T18:48:15Z


Alright I tracked down the problem. A fix is coming up. Thanks mangelasakis!

@mixxxbot
Copy link
Collaborator Author

Commented by: mangelasakis
Date: 2011-12-19T15:19:31Z


When will you upgrade the mixxx with the solution of this bug?

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2011-12-19T19:04:28Z


Mixxx 1.10 final will have the fix. If you'd like to test a pre-release
version that has the fix, you can download it here:

http://builds.mixxx.org/builds/release-1.10.x

On Mon, Dec 19, 2011 at 10:19 AM, mangelasakis wrote:

*** This bug is a duplicate of bug 768022 ***
https://bugs.launchpad.net/bugs/768022

When will you upgrade the mixxx with the solution of this bug?

--
You received this bug notification because you are a member of Mixxx
Development Team, which is subscribed to Mixxx.
https://bugs.launchpad.net/bugs/905776

Title:
Search queries not properly escaped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mixxx/+bug/905776/+subscriptions

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Committed.

@mixxxbot
Copy link
Collaborator Author

Duplicate of #5870

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug duplicate This issue is a duplicate of or superseded by another issue.
Projects
None yet
Development

No branches or pull requests

1 participant