Last modified: 2010-05-15 15:33:38 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 1159 - Bogus link table entries with l_from=0
Bogus link table entries with l_from=0
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-12-23 05:18 UTC by Angela
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Description Angela 2004-12-23 05:18:07 UTC
[[Template:In the news]] and [[Template:Cohort]] are shown on the edit screen of
new pages even though they are not used there. It doesn't happen on de, fr, or
aa, but it does on en.
Comment 1 Brion Vibber 2004-12-24 03:10:50 UTC
There are a bunch of bogus entries in the links table with l_from=0. Two of them were to template pages, and these were getting 
pulled in for the edit page.

I've manually removed those two entries, but there are still others and I don't know whether the source problem is still present. 
Changing summary to reflect general problem.
Comment 2 Zigger 2005-01-29 14:19:15 UTC
See also bug 1430 which includes avoiding the template list load for a new page.
Comment 3 Antoine "hashar" Musso (WMF) 2005-08-17 19:15:06 UTC
I have checked the links table on for several wikipedias (en, ja, de, fr)
and could not find any l_from=0 entry in the links table.

Most probably the issue is no more happening. Considering the issue
fixed somehow.

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