Last modified: 2010-09-23 14:56:32 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T27258, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25258 - "Sequence" namespace on Commons conflicts with some existent pages
"Sequence" namespace on Commons conflicts with some existent pages
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://commons.wikimedia.org/wiki/Seq...
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-09-23 11:48 UTC by Helder
Modified: 2010-09-23 14:56 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Helder 2010-09-23 11:48:43 UTC
Hi!

After the "Sequence:" namespace was enabled on Commons, some pages starting with "Sequence:" are not accessible anymore.

As an example, "Sequence:Wikijúnior:Alfabeto dos animais" appears in my contributions,
http://commons.wikimedia.org/w/index.php?title=Special:Contributions/Heldergeovane&withJS=MediaWiki:Gadget-rightsfilter.js&lifilterexpr=alfabeto

but is not shown when accessed directly:
http://commons.wikimedia.org/wiki/Sequence:Wikij%C3%BAnior:Alfabeto_dos_animais

I was told it is needed to run some cleanup script at Wikimedia Commons, but I'm not sure what is it...

So if someone could do that, I would appreciate ;-)

PS: The server admin log entry for this is at
http://wikitech.wikimedia.org/view/Server_admin_log#September_22
Comment 1 p858snake 2010-09-23 11:49:55 UTC
Can we hit who didn't run namespacedupes?
Comment 2 Sam Reed (reedy) 2010-09-23 11:51:03 UTC
<Nikerabbit> I'd like to file a another bug to make absolutely frigging sure that the script is run when new namespace is added
Comment 3 Roan Kattouw 2010-09-23 14:55:33 UTC
Fixed. The following two pages couldn't be moved:

... 11371140 (0,"Sequence:Cats") -> (104,"Cats") [[Sequence:Cats]]
...  *** cannot resolve automatically; page exists with ID 11566971 ***
...  *** old title Cats
...  *** new title Cats/DUPE
...  *** using suffixed form [[Sequence:Cats/DUPE]] ***
... resolving on page... ok.
... 11351901 (0,"Sequence:Test") -> (104,"Test") [[Sequence:Test]]
...  *** cannot resolve automatically; page exists with ID 11564996 ***
...  *** old title Test
...  *** new title Test/DUPE
...  *** using suffixed form [[Sequence:Test/DUPE]] ***
... resolving on page... ok.
Comment 4 Roan Kattouw 2010-09-23 14:56:32 UTC
(In reply to comment #2)
> <Nikerabbit> I'd like to file a another bug to make absolutely frigging sure
> that the script is run when new namespace is added
This is hard to enforce on the technical level. Namespaces are not added by running a script, but by editing the config and in some cases even by enabling extensions (e.g. LQT).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links