-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
Commented by: rryan Thanks for the informative report!
|
Commented by: mangelasakis 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. |
Commented by: mangelasakis 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... |
Commented by: rryan Alright I tracked down the problem. A fix is coming up. Thanks mangelasakis! |
Commented by: mangelasakis When will you upgrade the mixxx with the solution of this bug? |
Commented by: rryan Mixxx 1.10 final will have the fix. If you'd like to test a pre-release http://builds.mixxx.org/builds/release-1.10.x On Mon, Dec 19, 2011 at 10:19 AM, mangelasakis wrote:
|
Issue closed with status Fix Committed. |
Duplicate of #5870 |
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.
The text was updated successfully, but these errors were encountered: