[wp-trac] Re: [WordPress Trac] #2977: Username/Nickname with spaces
cannot delete it's own posts or comments
WordPress Trac
wp-trac at lists.automattic.com
Thu Jul 27 05:37:22 GMT 2006
#2977: Username/Nickname with spaces cannot delete it's own posts or comments
----------------------------+-----------------------------------------------
Reporter: hgfischer | Owner: mdawaffe
Type: defect | Status: new
Priority: high | Milestone: 2.0.4
Component: Administration | Version: 2.0.3
Severity: major | Resolution:
Keywords: |
----------------------------+-----------------------------------------------
Changes (by mdawaffe):
* owner: anonymous => mdawaffe
Comment:
hgfischer, nice catch!
This applies to users with username containing any character needing
urlencoding: space, @, etc.
Tangentially related to #2969.
The reason we had wp_clean_ajax_input() in trunk to urldecode $_POST was
because the old version of sack required it (it may have been double
encoding...? I don't recall). With the new version of sack in trunk,
wp_clean_ajax_input() was detrimental.
We still have the old version of sack in branches/2.0 (as we should), so
we need to decode there.
This should not be an issue elsewhere in the core. I believe branches/2.0
only deals with integers being sent by AJAX requests (except for on the
fly category addition which handles things on its own).
Patch looks good. Submitting as diff.
Note: this bug does not apply to trunk; everything is fine there.
--
Ticket URL: <http://trac.wordpress.org/ticket/2977>
WordPress Trac <http://wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list