Last modified: 2007-02-06 21:20:33 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 T10906, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8906 - Definition hacked???
Definition hacked???
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/Structure
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-06 21:00 UTC by Summer
Modified: 2007-02-06 21:20 UTC (History)
0 users

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


Attachments

Description Summer 2007-02-06 21:00:24 UTC
The definition for the word "structure" looks like it's been hacked. Or else you need to fire 
one of your writers...

Thanks, 
Summer M. 
summerrae@hotmail.com
Comment 1 Raimond Spekking 2007-02-06 21:02:37 UTC
A "normal" vandalism, see
http://en.wikipedia.org/w/index.php?title=Structure&diff=106070974&oldid=106070668,
please do not report these kind of errors to bugzilla.
Comment 2 Summer 2007-02-06 21:16:32 UTC
Please don't report these kind of errors? Wow, you can get sued for having such content 
accessible to site visitors under the age of 18...I was just trying to be helpful. A 
simple "thanks for the heads up" would have been a much more appropriate response. 
Comment 3 Rob Church 2007-02-06 21:20:33 UTC
The point is that this is a bug tracker, for problems with the MediaWiki
software or the Wikimedia servers, etc. We don't handle content issues, and we
never have; that's the whole point of wikis, and Wikipedia, Wikinews, etc.

Sometimes, newcomers don't understand this, which is fine; we point them in the
right direction. Raymond forgot to do that...the usual route is either to click
"edit" and change the page yourself to fix the problem, or to raise the issue on
the "discussion" page associated with the problematic page.

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


Navigation
Links