Timeline for wrong results of /search/advanced
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2016 at 14:48 | review | Suggested edits | |||
| Jun 2, 2016 at 19:27 | |||||
| May 18, 2016 at 3:07 | vote | accept | amit jha | ||
| May 11, 2016 at 5:55 | comment | added | amit jha | @BrockAdams also other questions are related but do not answer this question. they help but do not answer. | |
| May 11, 2016 at 5:48 | comment | added | amit jha | @BrockAdams the answers link given by you in the first comment is not not the required one. | |
| May 11, 2016 at 5:43 | vote | accept | amit jha | ||
| May 18, 2016 at 3:07 | |||||
| May 11, 2016 at 5:17 | comment | added | Brock Adams | If that's true -- and the OP was by no means clear on that point -- then the question should be closed as a duplicate of this, or this, or this, or one of about 4 other questions. | |
| May 11, 2016 at 4:31 | comment | added | Tim Stone♦ | It's not really. They searched on the site and got an answer as the second result, they searched with the API and didn't, because the API doesn't return specific answers as results | |
| May 11, 2016 at 4:24 | comment | added | Brock Adams |
The /search paths can return answers too. The question is poor and should be closed.
|
|
| May 11, 2016 at 0:13 | history | answered | Tim Stone♦ | CC BY-SA 3.0 |