Last modified: 2005-10-29 02:54:58 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 T3286, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 1286 - Edits in articles omitted from history or contribs
Edits in articles omitted from history or contribs
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 1246 (view as bug list)
Depends on:
Blocks: db-repl-track
  Show dependency treegraph
 
Reported: 2005-01-08 11:29 UTC by PS
Modified: 2005-10-29 02:54 UTC (History)
1 user (show)

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


Attachments

Description PS 2005-01-08 11:29:36 UTC
I've been editing "Cultural and historical background of Jesus" as user 
FT2.

On several occasions today I have posted edits to this article, which did 
not appear in history or in my contributions.  Nonetheless they appeared 
in the current version of the article -  but were not reflected by DIFF 
when i compared current to previous articles.

Mysteriously some time later one of the edits appeared.  But then I 
posted another edit, and the same happened again.

If more details are needed please contact me at my email address.  Not 
sure what else is useful.
Comment 1 Hendrik Brummermann 2005-01-08 11:38:25 UTC
Please verify whether the versions appear a little bit later. I think this is
related to replication lag.
Comment 2 Brion Vibber 2005-01-29 07:49:22 UTC
Given lack of information, this sounds like existing replication lag issues.
Comment 3 Zigger 2005-05-08 20:35:26 UTC
This occurred in the last few hours on en.wikipedia.org.  Presumably due to
database replication lag or log reload.  Re-opening to avoid duplicate reports,
because it happens, to remind people of the impacts of lag, and despite the
cause being known.
Comment 4 Zigger 2005-05-10 13:30:55 UTC
*** Bug 1246 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