Opened 14 years ago
Closed 14 years ago
#14905 closed defect (bug) (fixed)
Plugin Search Term gets lost on Activation
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | 3.1 | Priority: | normal |
| Severity: | normal | Version: | 3.0 |
| Component: | Plugins | Keywords: | |
| Focuses: | Cc: |
Description
With Javascript Switched of on Trunk, searching for a plugin in the Backend does work.
But when such a search has been runned and a plugin of the serach result is being activated, after activation the plugin screen returns to a search result w/o searching for anything.
The search term is lost.
Expected result: The search term must be preserved with the request, not removed.
This problem exists in 3.0.1 (with a notice even) and 3.1-alpha.
Change History (8)
#4
@
14 years ago
- Milestone changed from 3.1 to 3.0.2
- Resolution fixed deleted
- Status changed from closed to reopened
re-opening for 3.0.x consideration
#5
@
14 years ago
Patch as is will leave a lot of useless &s= scattered about. As long as that doesn't trigger any search conditions on account of it being empty though, I suppose that's fine.
#6
@
14 years ago
Patch as is will leave a lot of useless &s= scattered about.
It does, But the paged variable was already basically useless in 95% of cases.. I personally don't mind there being a empty request variable set as long as they dont start a waterfall (ie. all the links on the page then include it, etc)
(In [15697]) Preserve search terms on plugin management pages during actions. Fixes #14905 for trunk.