[wp-trac] [WordPress Trac] #19373: wp_insert_post() should not contain current_user_can() checks
WordPress Trac
wp-trac at lists.automattic.com
Mon Nov 28 21:48:39 UTC 2011
#19373: wp_insert_post() should not contain current_user_can() checks
-----------------------------------+-----------------------------
Reporter: alexkingorg | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: Taxonomy | Version: 3.0
Severity: major | Resolution:
Keywords: 3.4-early needs-patch |
-----------------------------------+-----------------------------
Comment (by nacin):
Replying to [comment:9 johnbillion]:
> Replying to [comment:8 nacin]:
> > Emphasizing needs-patch on this one. Someone will probably need to
step up here.
> As you mentioned it, if someone is working on a patch for a given ticket
is it a best practice to assign the ticket to yourself so others know it's
being worked on?
Not typically necessary. I would just go for it and post a patch. Owners
are typically more useful for those in charge of major tasks for a release
(and the bugs that inevitably follow) and for committers to keep track of
what they are watching over.
If multiple patches end up on the ticket, that's not a bad thing. It's
good to see multiple approaches.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/19373#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list