Last modified: 2012-12-04 23:06:04 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 T44697, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42697 - Searching for duplicates doesn't work
Searching for duplicates doesn't work
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-04 21:15 UTC by Chad H.
Modified: 2012-12-04 23:06 UTC (History)
3 users (show)

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


Attachments

Description Chad H. 2012-12-04 21:15:40 UTC
Since upgrading, the search for dupes feature doesn't seem to work. When inputting a new bug (like the one I'm on now), after typing a summary, the text "Searching for possible duplicates..." shows up and doesn't seem to do anything after that.
Comment 1 Andre Klapper 2012-12-04 22:59:24 UTC
> and doesn't seem to do anything after that.

What does that mean? 
Showing """Searching for possible duplicates..."" forever?

Here it shows ""Searching for possible duplicates..."" and a bit later it displays ""No possible duplicates found.""

Going to https://bugzilla.wikimedia.org/enter_bug.cgi?product=Commons%20App and entering 
      Searching for duplicates doesn't work
as the summary it displays two proposals (41703, 41704).
Comment 2 Chad H. 2012-12-04 23:02:43 UTC
(In reply to comment #1)
> What does that mean? 
> Showing """Searching for possible duplicates..."" forever?
> 

This one.
Comment 3 Chad H. 2012-12-04 23:03:25 UTC
Although, now it seems to work just fine. Dunno what was up.
Comment 4 Andre Klapper 2012-12-04 23:06:04 UTC
Ah well. If it happens again, the browser would be good to know.
I'm using Firefox 16.0.2 on Fedora 16 on this machine.

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


Navigation
Links