Last modified: 2014-05-12 22:02:30 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62354, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60354 - Search indexing affected by less-than sign?
Search indexing affected by less-than sign?
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-22 19:43 UTC by Peter Ford
Modified: 2014-05-12 22:02 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Peter Ford 2014-01-22 19:43:03 UTC
In MediaWiki with no search extensions, I edit a normal wiki page. I place the following sentence (if you can call it that) on a line by itself:

  One < two butundeniably seven > six.

And then try using MediaWiki's search functionality to search for 'butundeniably'. I get: "There were no results matching the query". I suspect the less-than sign is relevant in this behaviour.

Then change the word "two" to be the corresponding digit "2", resulting in this:

  One < 2 butundeniably seven > six.

Now the search successfully finds the page.



I've discussed this on the support desk. One other user reported a similar symptom.  https://www.mediawiki.org/w/index.php?title=Project:Support_desk&offset=20140103140951&limit=20#Search_indexing_affected_by_less-than_sign.3F_35699
Comment 1 Peter Ford 2014-01-22 19:53:58 UTC
Sorry, here is a more permanent link for my support desk discussion: https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Search_indexing_affected_by_less-than_sign%3F_%282%29
Comment 2 Chad H. 2014-05-12 22:02:30 UTC
Known bug in MWSearch/lsearchd that's not being fixed. We don't have this problem in Cirrus/Elasticsearch so marking WONTFIX.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links