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 All Fields Not Providing Expected Results (lowercase vs. uppercase letters) #2375

Open
jamiers99 opened this Issue Mar 18, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@jamiers99

jamiers99 commented Mar 18, 2018

I wasn't sure if I was supposed to link this to closed ticket #1770

Technical details regarding my environment

  • YOURLS version: 1.7.2
    • Plugins enabled: 404 Not Found. Allow Forward Slashes in Short URLs, Don't encode/decode, Short URL so what
  • PHP version: 5.6.30
  • Any other useful information depending on context (server OS & version, MySQL version, browser version, …): MySQL 5.5.51-38.2, Chrome 64.0.3282.186

Bug description

What is the current behavior?
I notice that when I use the search at the bottom of the page, that Title is not being searched for upper OR lower case letters. I currently have 1.7.2 with plugins noted above:

I have two items in my entries for titles:

  • Bulk Distribution Operations ILT
  • Bulk Distribution Fundamentals WBT
    When searching for 'bulk' no entries appear. When searching for 'Bulk' both entries appear.

But... I have dozens of entries that show WBT in the title:
blah blah WBT
blah2 WBT
Blah Blah Blah3 WBT
When searching 'wbt' they appear, when searching 'WBT' they appear, but when searching 'Wbt' or 'wBt' they do not appear.

This is a bug because… searching is not consistent with expected behavior of user. Lower case letters are typically used in search engine queries.

Reproducible bug summary

  1. Type word into search box
  2. results not expected
@jinbo-yu

This comment has been minimized.

jinbo-yu commented Mar 20, 2018

if url contains char "%", the result is wrong too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment