Last modified: 2005-05-22 17:18:00 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 T2021, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21 - Accidentical overwriting of newest version
Accidentical overwriting of newest version
Status: CLOSED WORKSFORME
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-08-14 04:55 UTC by Timwi
Modified: 2005-05-22 17:18 UTC (History)
1 user (show)

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


Attachments

Description Timwi 2004-08-14 04:55:28 UTC
BUG MIGRATED FROM SOURCEFORGE
    http://sourceforge.net/tracker/index.php?func=detail&aid=1008236&group_id=34373&atid=411192
    Originally submitted by Nobody/Anonymous - nobody  2004-08-12 22:28


    (Is there really no Wikipage to discuss this first
before submitting a report?)


In
http://en.wikipedia.org/wiki/Wikipedia:Village_pump#The_B-Movie_Bandit
the possibility was raised, that the suspected
vandalism may be in fact a software problem which let
some users not see the newest version. And let them
overwrite it with an edited older version.

Now there was a similiar case in [[Unicode]], but not
with an anon, so you can ask him, what really happened,
see  [[User talk:Bletch]]

[[Pjacobi]]

    ---- Additional comments ----
Comment 1 Wil Mahan 2004-09-17 18:10:51 UTC
On the talk page Bletch said "I am not sure if it Wiki's fault of a simple
oversight on my part". Since the only other evidence for this bug is speculation
about an anonymous vandal, this bug seems too vague to work with. Unless there
is a way to reproduce this bug, it should be closed IMHO.
Comment 2 Brion Vibber 2004-09-17 19:00:11 UTC
Could have been accident or temporary caching problem which has since been resolved. Resolving as 
WORKSFORME since there is no further report of similar.
Comment 3 River Tarnell 2005-05-22 17:18:00 UTC
CLOSED not verified, no evidence it's a bug. 

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


Navigation
Links