Last modified: 2012-05-05 19:38:14 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 T17819, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15819 - <references/> fails after Special:Prefixindex
<references/> fails after Special:Prefixindex
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Cite (Other open bugs)
unspecified
All All
: Low major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://test.wikipedia.org/wiki/Prefix...
: patch
: 36177 (view as bug list)
Depends on:
Blocks: 16767
  Show dependency treegraph
 
Reported: 2008-10-03 21:13 UTC by STyx
Modified: 2012-05-05 19:38 UTC (History)
8 users (show)

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


Attachments
proposed fix: clear state only if called from $wgParser (736 bytes, patch)
2009-02-02 23:59 UTC, P.Copp
Details

Description STyx 2008-10-03 21:13:47 UTC
A lost reference<ref>A lost reference</ref>.
 {{Special:Prefixindex/Template:X}}
 Another reference<ref>Another reference</ref>.
 ==Note==
 <references/>


"A lost reference" is lost.
Comment 1 Aaron Schulz 2008-12-12 14:50:11 UTC
I can't reproduce this locally
Comment 2 Gurch 2008-12-13 16:57:09 UTC
Doesn't happen on en.wikipedia either. But both are using the same MediaWiki version, so it's either an extension that's on test.wikipedia but not en.wikipedia or something in test.wikipedia's config.
Comment 4 P.Copp 2009-02-02 23:59:39 UTC
Created attachment 5773 [details]
proposed fix: clear state only if called from $wgParser

This happens, because there is only one Cite object, but two parsers ($wgParser and $wgMessageCache->mParser). Cite->clearState() should only trigger on calls by $wgParser, else it loses all references up to this point.

Easy fix attached.
Comment 5 Christian Neubauer 2010-03-29 14:40:24 UTC
This fix fixes bug 16767 as well
Comment 6 db [inactive,noenotif] 2010-11-27 21:11:38 UTC
maybe related bug 20748
Comment 7 Kevin Brown 2011-05-27 16:53:02 UTC
Applied P.Copp's patch and fixed in r88971.
Comment 8 db [inactive,noenotif] 2012-05-05 19:38:14 UTC
*** Bug 36177 has been marked as a duplicate of this bug. ***

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


Navigation
Links