On Tuesday 30 March 2010 12:49, ccornell - OpenOffice.org wrote: > On 03/30/10 11:59 AM, Nino Novak wrote: > > On Tuesday 30 March 2010 10:25, ccornell - OpenOffice.org wrote: > >> ... > >> page 6663 (:General) doesn't match self. > >> DRY RUN: would rename 6663 (100,'General') to (100,'General') > >> page 6664 (:General) doesn't match self. > >> DRY RUN: would rename 6664 (101,'General') to (101,'General') > > > > could you provide the textual names of custom namespaces 100 and > > 101? > > > > I do not see them with the siteinfo/namespaces query. So they might > > be not existing. > > Good question. > > Namespaces in the 100+ range are usually reserved for custom > namespaces that are defined in a MediaWiki based Wiki. In the > OOoWiki we're not using anything beyond the default 18 Namespaces
(plus 274 and 275 [Widget resp Widget talk] from Widgets extension.) > The default 18 namespaces are documented here: > http://meta.wikimedia.org/wiki/Help:Namespace I used the api query for this instead. BTW - I was able to use it without being logged in, so there might be a security hole in the installation (ok, I did not try api calls with write permissions - but perhaps this should be tested in detail) > Just guessing here... the broken pages that show up in the 100 and > 101 namespaces are all pages that start with a colon (even numbers > are content pages, and odd are talk pages). It's likely the script > thinks that the pages belong to the undefined namespace because of > that leading colon. That's what I thought, too. As the colon separates the namespace name and the pagename, the pages could have been attached to the non-existing namespace 100/101 by error (e.g. by parsing an empty string as namespace name) > It's possible that when I run the maintenance script the pages will > end up attached to the 100 and 101 namespace and not be immediately > accessible... but they aren't accessible now as it is, so this isn't > a loss. If this happens I could try enabling a temp namespace at 100 > and 101 to see if we would be able to view the lost/broken pages that > got mistakenly attached to a new undefined namespace. yep. you could try to declare a custom namespace 100/101 and see if the pages would turn accessible then even without the maintenance script being run before. Nino --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
