Last modified: 2012-01-11 18:03:45 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 T35629, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33629 - Extraneous 'John Locke Essay' text appearing in article.
Extraneous 'John Locke Essay' text appearing in article.
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-10 02:54 UTC by Den
Modified: 2012-01-11 18:03 UTC (History)
2 users (show)

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


Attachments
Screenshot of extra text on wikipedia article (427.29 KB, image/jpeg)
2012-01-10 02:54 UTC, Den
Details

Description Den 2012-01-10 02:54:21 UTC
Created attachment 9831 [details]
Screenshot of extra text on wikipedia article

I noticed this bug in the History section of the wikipedia article for 'Ampersand'. (http://en.wikipedia.org/wiki/Ampersand)

Large chunks of text are repeated in the output of the article. Chunks of text appear to be copied from wikipedia article for 'Essay' and are unrelated to the article viewed. 

The extra text does NOT appear when editing the article - seems to only show up when viewing the article and, can be seen in HTML source code too. The bug appeared in current browsers, Safari, Chrome, Firefox and Wikipedia mobile app.

The extra text shows up in the first sentence of History section that reads.. 
'The ampersand can be (.. extra text..) traced back to the 1st century A.D.' 

No unusual code appears in that location when editing the article.

See attached screen shot.

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


Navigation
Links