[wp-xmlrpc] Best practise for validating a site connection

[Daniel Jalkut]

Not saying this is the best practice, but to complete your menu of differing behaviors: in MarsEdit a successful "getRecentPosts" is pretty much the test for whether a configuration was made correctly or not.

(I don't use getUsersBlogs because the setup sequence in MarsEdit is centered around providing the home page URL to a single blog).

If you decide to do some kind of "capabilities" method, may I suggest you follow the lead of the "API is disabled" error message, and include URLs in the response to the page where a particular capability can be modified. I am thinking something like (in pseudo-XML):

<capabilities>
	<capability name="xmlrpcAccess" enabled="false" settingURL="http://myblog/admin/settings.php">
	<capability name="editPosts" enabled="true" settingURL="etc…">
</capabilities>

Though, come to think of it, maybe this should all be shoe-horned into the wlwmanifest file?

Daniel

On Oct 11, 2010, at 6:07am, Peter Westwood wrote:

> Hi All,
> 
> I wonder what you all think is the best way to validate that the url/username/password combo a user has entered in your app is good enough to continue with?
> 
> It seems different apps have different ideas.
> 
> Some seem to create drafts, some list users blogs, some publish posts!
> 
> I wonder if an extra API would be beneficial here - or an extended better version of blogger.getUsersBlogs which gave you info about the capabilities of the user with respect to a site?
> 
> Cheers
> -- 
> Peter Westwood
> http://blog.ftwr.co.uk | http://westi.wordpress.com
> C53C F8FC 8796 8508 88D6 C950 54F4 5DCD A834 01C5
> 
> _______________________________________________
> wp-xmlrpc mailing list
> wp-xmlrpc at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-xmlrpc