Last modified: 2011-03-13 18:05:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9913 - Transcluding a template which does not exist is sometimes treated as speedy-delete tagging
Transcluding a template which does not exist is sometimes treated as speedy-d...
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC Windows 98
: Lowest normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-14 19:32 UTC by Anthony Appleyard
Modified: 2011-03-13 18:05 UTC (History)
0 users

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


Attachments

Description Anthony Appleyard 2007-05-14 19:32:43 UTC
I am an admin in the English Wikipedia. Sometimes an English Wikipedia page
which tries to transclude a template which does not exist, is treated as if it
was in one of the to-be-speedy-deleted categories, and appears in the
to-be-speedy-deleted list, although it contains no {{db-...}} tag. If I create
the non-existent template as {{}} (i.e. a dummy template), the affected page no
longer appears in the to-be-speedy-deleted list.
Comment 1 Rob Church 2007-05-14 20:29:20 UTC
Example?
Comment 2 Anthony Appleyard 2007-05-14 21:21:01 UTC
On 13 May 2007 I was going through the to-be-speedy-deleted lists. The list
(catalog) for db-author contained several files in a user's filespace. Those
files did not have a speedy-delete tag, but they were allegedly in
[[Category:Candidates for speedy deletion by user]]. I looked at one of them in
edit mode. The list of transcluded templates at the end included two red names,
for nonexistent templates: one of them was [[User:The Haunted Angel/General
Userboxes]]. I created those two templates as dummy templates {{}} . I refreshed
the display of [[Category:Candidates for speedy deletion by user]], and those
spuriously listed files went away.

Later that day I found that [[User:The Haunted Angel/General Userboxes]] had
existed before and shortly before this someone deleted it "CSD G7: Author
Requests Deletion", although it did not contain a speedy-delete tag.

I have had similar cases before. That is why, when I delete a speedied page, I
always read it to check that it does contain a speedy-delete tag.
Comment 3 Anthony Appleyard 2007-05-14 21:21:20 UTC
On 13 May 2007 I was going through the to-be-speedy-deleted lists. The list
(catalog) for db-author contained several files in a user's filespace. Those
files did not have a speedy-delete tag, but they were allegedly in
[[Category:Candidates for speedy deletion by user]]. I looked at one of them in
edit mode. The list of transcluded templates at the end included two red names,
for nonexistent templates: one of them was [[User:The Haunted Angel/General
Userboxes]]. I created those two templates as dummy templates {{}} . I refreshed
the display of [[Category:Candidates for speedy deletion by user]], and those
spuriously listed files went away.

Later that day I found that [[User:The Haunted Angel/General Userboxes]] had
existed before and shortly before this someone deleted it "CSD G7: Author
Requests Deletion", although it did not contain a speedy-delete tag.

I have had similar cases before. That is why, when I delete a speedied page, I
always read it to check that it does contain a speedy-delete tag.
Comment 4 Aaron Schulz 2007-05-14 21:37:24 UTC
Please give a repeatable set of instructions to duplicate this behavoir.
Comment 5 Anthony Appleyard 2007-05-14 22:15:29 UTC
I do not know that it is reliably repeatable. It "happens sometimes". OK, I
know, intermittent faults are a nuisance. But it happens sometimes.
Comment 6 Anthony Appleyard 2007-05-14 22:17:17 UTC
It seems to happen when a file tries to transclude a template which has been
recently deleted. 
Comment 7 ChemicalBit 2007-05-15 17:44:47 UTC
A way to duplicate this behaviour (although it's a intermittent trouble, so this
way doesn't work every time) is:

*Create a page A
*Create a page B (for example a template, or a subpage)
*Edit page A and transclude page B in it.
*Edit page B and add (transclude) the template (let's call it C) that request
speedy-deleting. (without noinclude instuction)
*As template C add a <includeonly>[[Category:X]]</includeonly> instuction, both
A and B pages are showed in the category:X page (which lists all the page marked
for speedy-deleting.
*Delete the B page.
*Now the A page may be still listed in the category:X page (may = it's a
intermittent trouble)
*If you look at the A page, there is no category:X sign at the botton.
*Page A will goes away from category:X after an indeterminate time. 


Further information: 

*the time of "phantom" staying in Category:X is inteterminate. Pages go out
without a "First in, first out" way: (In a test of our, a page B-2 was delteted
some hours after the deletion of B-1. A-2 (related to B-2) went out after less
than 1 hour, but A-1 (related to B-1) were still there!!)
*I have not checked if the trouble may sometime happends if template C is
transcluded in B page with a noinclude. We can test it, if you think that this
could be usefull.
*I can rememember some trouble like this some time ago (even months and months,
I think) , but it looks like that these troubles have become more frequent in
the last week).
*Tests done on it.wikpedia.org

Comment 8 Brion Vibber 2007-05-15 17:51:06 UTC
This is to be expected when you mark templates as speedy.

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


Navigation
Links