Last modified: 2012-03-14 18:35:43 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 T36869, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34869 - Search not properly working on mr.wikisource.org
Search not properly working on mr.wikisource.org
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
unspecified
All All
: Normal critical (vote)
: ---
Assigned To: Robert Stojnic
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-01 20:03 UTC by Shantanoo
Modified: 2012-03-14 18:35 UTC (History)
1 user (show)

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


Attachments

Description Shantanoo 2012-03-01 20:03:25 UTC
When user searches for some word, even if it is available on the wiki pages, it is not displayed.

e.g.

on http://mr.wikisource.org 'साने' is displayed. But when user searches it, result is 0.

http://mr.wikisource.org/w/index.php?search=%E0%A4%B8%E0%A4%BE%E0%A4%A8%E0%A5%87&title=%E0%A4%B5%E0%A4%BF%E0%A4%B6%E0%A5%87%E0%A4%B7%3A%E0%A4%B6%E0%A5%8B%E0%A4%A7%E0%A4%BE
Comment 2 Shantanoo 2012-03-13 19:29:04 UTC
Changing importance to 'Critical'. It getting difficult to make sure that duplicate content is not added as search is not working properly.
Comment 3 Shantanoo 2012-03-14 18:26:05 UTC
Did work. Screenshot available at https://skitch.com/e-shantanoo/8kba8/
Comment 4 Shantanoo 2012-03-14 18:26:35 UTC
(In reply to comment #3)
> Did work. Screenshot available at https://skitch.com/e-shantanoo/8kba8/

Did *not* work.
Comment 5 Robert Stojnic 2012-03-14 18:35:43 UTC
I've only fixed the search (your first link from initial bug report), the issue with PrefixSearch (comment 1) is a separate issue, not sure what is wrong there. 

Since these are separate issues it might be a good idea to file it under another bug. Since the initial issue is fixed, marking as fixed.

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


Navigation
Links