Opened 14 years ago
Closed 14 years ago
#16548 closed defect (bug) (fixed)
Plugin searches drop spaces with further action
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.3 | Priority: | normal |
Severity: | normal | Version: | 3.1 |
Component: | Administration | Keywords: | has-patch commit 3.3-early |
Focuses: | Cc: |
Description
Steps to reproduce:
- Search for a valid plugin name with a space in it
- Activate it
- The space will be dropped from the redirected URL by
wp_redirect()
sanitization
Attachments (3)
Change History (17)
#3
@
14 years ago
@SergeyBiryukov the patch doesn't change anything? Steps to reproduce still cause the same issue.
#5
follow-up:
↓ 12
@
14 years ago
This comes back to the usage of "...&s=$s"
which translates to "...&s=Add From Server"
which is obviously wrong.
Given the sheer number of redirects it's used in, This patch simply urlencodes it when it gets it from the request.
#6
@
14 years ago
- Keywords commit added
- Milestone changed from Awaiting Review to 3.1
Bumping to 3.1 for another dev to check
#7
follow-up:
↓ 8
@
14 years ago
Search for a valid plugin name with a space in it
I assume we're talking about the plugin's directory name, not the "Plugin Name:" header.
Also, is this a regression?
#8
in reply to:
↑ 7
@
14 years ago
Replying to scribu:
I assume we're talking about the plugin's directory name, not the "Plugin Name:" header.
No, we are talking about the plugin name, e.g. "Hello Dolly"
Also, is this a regression?
No - it's actually worse in 3.0.x because the search query is emptied, and you get this notice:
Notice: Undefined variable: total_search_plugins in wp-admin\plugins.php on line 475
#10
@
14 years ago
- Keywords 3.2-early added
- Milestone changed from 3.1 to Future Release
Per bug scrub, punting to 3.2.
#12
in reply to:
↑ 5
@
14 years ago
Replying to dd32:
Given the sheer number of redirects it's used in, This patch simply urlencodes it when it gets it from the request.
Looks like urldecode()
for display is not required, since $s
is restored to non-encoded form in wp_reset_vars()
via $wp_list_table->prepare_items()
.
Maybe we should drop the search query var when doing other actions?