https://bugzilla.wikimedia.org/show_bug.cgi?id=25648
Brion Vibber <br...@pobox.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #7758|0 |1
is obsolete| |
--- Comment #7 from Brion Vibber <br...@pobox.com> 2010-10-26 22:19:07 UTC ---
Created attachment 7759
--> https://bugzilla.wikimedia.org/attachment.cgi?id=7759
Tweaked ApiRSD patch
I've done a little testing and enhanced the patch a bit:
* added the <link> to page header
* tweaked the XML output to fix some attribute vs child-element oddities
* tweaked the hook point so we can hand a slightly simpler array to extensions
to use.
This looks about right to me (though I wanna double-check in a bit), and I can
add some sample extension API info like so:
$wgHooks['ApiRsdServiceApis'][] = 'barfo';
function barfo(&$apis) {
$apis['Atom'] = array(
'apiLink' => wfAppendQuery(wfScript('api'), array('action' =>
'atompub')),
);
$apis['Twitter'] = array(
'apiLink' => wfAppendQuery(wfScript('api'), array('action' =>
'twitapi')),
'docs' => 'http://apiwiki.twitter.com/Twitter-API-Documentation',
'settings' => array(
'OAuth' => false,
)
);
return true;
}
Things to double-check:
* confirm all is well with it served as generic application/xml (should be
fine)
* double-check if we're required to make URLs fully-qualified (in which case it
wouldn't hurt to enforce it on extension-provided URLs)
* test: throw in WordPress and Twitter API points as in the ext example above,
and make sure that WordPress and StatusNet Android/iPhone clients actually pick
them up when given the wiki's base URL.
May need to add hook doc entry.
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
