On 08/06/2010 11:51 AM, Roan Kattouw wrote:
2010/8/6 Nikola Smolenski<smolensk(a)eunet.rs>rs>:
I have recently fixed some of its shortcomings
and onward) and I
believe that the extension is now ready for practical use. Could anyone
interested review the code and see if it is technically good enough, and if
there is anything else that needs to be done? And if it is good enough and
there is nothing critical missing, what would be the steps to test it in the
real world and actually deploy it?
When it has passed review, I suppose we could set up a few wikis at
and test it there. It was originally set up
for the usability initiative but it seems to be used for increasingly
random testing purposes now, and we have no other proper place for
Great! :) Note that, for testing purposes, it is possible to keep the
pages of the central wiki in a separate namespace or as subpages.
- Reading the
links from a foreign database instead of via the API. Is there
a "proper" way to do this?
Yes. You can obtain a connection to a foreign DB with wfGetDb(
DB_SLAVE, array() 'wikiID' ); . Both the wiki ID and the API URL can
be obtained from the interwiki table now (that is, there are fields
for them, we're not actually filling those fields yet), as part of
Peter's work on the iwtransclusion branch for GSoC. How have you been
obtaining API URLs anyway?
I'm using $wgInterlanguageExtensionApiUrl variable that has to be set in
links on dependent wikis when deleting, undeleting etc. articles on
the central wiki.
This is something the iwtransclusion branch also has to address. The
current plan is to do that using a global templatelinks table.
Interlanguage extension was lucky in that the articles that need to be
updated are exactly the ones that the interwikis link to :)