[wp-trac] [WordPress Trac] #26706: Allow custom authentication handlers for all requests
WordPress Trac
noreply at wordpress.org
Tue Mar 4 20:02:00 UTC 2014
#26706: Allow custom authentication handlers for all requests
------------------------------+------------------
Reporter: rmccue | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 3.9
Component: Users | Version:
Severity: minor | Resolution:
Keywords: has-patch commit | Focuses:
------------------------------+------------------
Comment (by nacin):
What about determine_current_user? It is imperative, like 'authenticate'.
We discussed "current_user_id" in IRC, but that sounds more like a filter
in get_current_user_id(), not the determination of the current user. We
then discussed set_current_user_id, which sounds more like it belongs in
wp_set_current_user(), and indeed already has a set_current_user action.
Ultimately, the only reason why get_currentuserinfo() isn't a part of
wp_get_current_user() is the issues of things being pluggable. So maybe
"current_user" does actually work. It pairs nicely with set_current_user,
though it doesn't run every time wp_get_current_user() is run, just on
initialization. (Also, as just pointed out in IRC, it implies returning an
object, not an ID.)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/26706#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list