https://bugzilla.wikimedia.org/show_bug.cgi?id=16288

--- Comment #4 from Reedy <[email protected]> 2011-03-20 00:50:29 UTC ---
(In reply to comment #0)
> Although this is very Wikimedia specific, consider adding information whether 
> a
> wiki's database has been closed (locked permanently) or not. There are many
> closed wikis out there, e.g.
> http://aa.wikipedia.org/w/api.php?action=query&meta=siteinfo
> 
> Currently, readonly="" shows that a database has been locked; temporarily or
> indefinetly. But an empty "" looks like "undefined"/"no". You  could either 
> add
> "yes"/1, and/OR for closed wikis even "closed".


readonly="" is the typical boolean way we do stuff. If it doesn't exist, it's
false.

(In reply to comment #2)
> Would be good if sitematrix not only indicated whether a wiki is readonly, but
> also whether the API is enabled at all there. Currently, trying an API call on
> a wiki where the API is disabled completely just returns a text "MediaWiki API
> is not enabled for this site. Add the following line to your
> LocalSettings.php&lt;pre&gt;%lt;b&gt;$wgEnableAPI=true;&lt;/b&gt;&lt;/pre&gt;"
> which is rather unhelpful for automated processing. For instance, when using
> dynamically generated script-elements with a callback: what we get back isn't
> even Javascript. Hence we need a way to ensure that we don't even try API 
> calls
> on such wikis. Sitematrix flagging wikis with disabled APIs would be one way.
> Or is there some other way to do this already?

Logged as bug 28126, as it has some overlap of the issue, but not completely...

-- 
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
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to