Opened 14 years ago
Closed 14 years ago
#16546 closed defect (bug) (worksforme)
Plugin Backend search does not work at all
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | WordPress.org | Priority: | normal |
Severity: | normal | Version: | 3.0.5 |
Component: | WordPress.org Site | Keywords: | |
Focuses: | Cc: |
Description
Vanilla 3.0.5 install on bluehost client system, wanted just to install "hotfix" via plugin search in backend - no luck.
Search results are in no way interacting to what I input.
Just wanted to let you know.
Change History (7)
#2
@
14 years ago
- Component changed from General to WordPress.org site
- Milestone changed from Awaiting Review to WordPress.org
Working fine for me on Plugins -> Add New.
Tested 3.1 and branches/3.0, WordPress code seems fine, API Seems working from my connection.
What are the results you are seeing? A screenshot would be useful to help determine what the results are that are being returned. just search for something common, such as 'hotfix' since that's what's brought it up.
Setting to WordPress.org as this sounds like an API issue
#4
@
14 years ago
(I knew of the WPDEVEL posts already that's why I concerned reporting) Results are just a default results for "anythign". Regardless what you enter, you will see the same results. I can not make a stance on "whatever/any" criterie that is causing this by classifying my input. I just can't classirfy what I input, the result is always the same. Multiple pages of plugins offered, but it is totally unreleated (and always the same) regardless what I input.
sorry for not being able ot be more speicifc, it's just that it does not amkes a difference what I enter as terms for search, regardless of the number of chars, even empty.
I hope this made my report more clear.
#5
@
14 years ago
sorry for not being able ot be more speicifc, it's just that it does not amkes a difference what I enter as terms for search, regardless of the number of chars, even empty.
That's exactly why I wanted to see the results, From the results, I can at least guess which view the API is showing, from there I can work out what could possibly be wrong.
I've checked it from my local machine and a Dreamhost US account, both are fine.
just validated against CRC32 checksums against latest.zip, all files on host have the same checksums.