[wp-xmlrpc] wpmu / adding users/sites/any other admin

[Alan Castonguay]

This came up on wp-hackers but didn't get much response. Any thoughts,  
or should I just start hacking up an implementation?

Alan J Castonguay



Begin forwarded message:

> From: Alan Castonguay <alan at verselogic.net>
> Date: April 6, 2009 5:13:44 PM GMT-04:00
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] wpmu / adding users/sites/any other admin
> Reply-To: wp-hackers at lists.automattic.com
>
>> Alan, how about "gaping pits of hell"?
> heh. =)
>
> As noted, there's a lot of configurables in the Wordpress admin  
> interface that are not exposed by either xmlrpc or atompub. The  
> xmlrpc function "wp_getAuthors" will provide user_id, user_login,  
> display_name, but there is no method to Edit existing user/usermeta,  
> Register new users, or Delete existing ones.
>
> The only fleshed out implementation of user management via atompub  
> that I'm aware of is Google's GDATA API for Provisioning on Google  
> Apps (for Premier and Education Edition). This seems well thought  
> out, and at least some of the decisions can be borrowed.
>
> http://code.google.com/apis/apps/gdata_provisioning_api_v2.0_developers_protocol.html#Create_Account_Example
>
> Gallery3's API is supposed to provide user registration and editing: http://codex.gallery2.org/Gallery3:API:REST
> Second Life's API supports user registration: http://wiki.secondlife.com/wiki/Registration_API
>
> A proper implementation has to start somewhere. So, what thinks  
> people of creating the following endpoints, and defining an atom  
> entry for a "user"? I'm not sure if this can borrow from hCard or  
> the DiSo project.
>
> + http://blog.example.com/(wp-)app.php/user/{id} or {username}?
> + http://blog.example.com/(wp-)app.php/users/{page}?
>
>
> Alan J Castonguay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://comox.textdrive.com/pipermail/wp-xmlrpc/attachments/20090411/d163375d/attachment.htm