Last modified: 2006-08-29 18:25:11 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 7166 - Recent changes to parser caching interfere with Cite
Recent changes to parser caching interfere with Cite
Status: RESOLVED DUPLICATE of bug 7162
Product: MediaWiki extensions
Classification: Unclassified
Cite (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-08-29 18:24 UTC by Robert Rohde
Modified: 2006-08-29 18:25 UTC (History)
0 users

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


Description Robert Rohde 2006-08-29 18:24:00 UTC
It appears that recent changes to the way that parser caching is handled are causing 
unexpected behavior from Cite when references are present.

I believe the change creating the problem is revision 16211 to OutputPage.php that tstarling 
made on the 24th.

For examples of the problem see: 
(showing a large number of "blank" references at the start)

Or simply edit any page employing Cite.  (If section editting, the bug will occur if the 
section has references or if the whole page is editted.)

Also Wikipedia:Village_pump_%28technical%
29#Mysterious_problem_involving_footnotes_and_citation_templates, for discussion.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-08-29 18:25:11 UTC

*** This bug has been marked as a duplicate of 7162 ***

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