Last modified: 2006-02-22 21:07:15 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 T5302, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 3302 - Talk page reverts to older state on new edits
Talk page reverts to older state on new edits
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-08-30 07:19 UTC by Owen Lloyd
Modified: 2006-02-22 21:07 UTC (History)
0 users

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


Description Owen Lloyd 2005-08-30 07:19:18 UTC
The talk page of this article tends to revert to an earlier state on new edits,
apparently to a state from July 28. It has been suggested that it only occurs
when using section editing, although this can't be confirmed. The software
places the edited or new section in the midst of the older subheadings of the
archived copy, while everything else is removed. It occurs about every 5th edit
to the page. I have no suggestions as to why it seems to freeze up and revert to
this earlier status.

It was first reported here:

And most recently occurred a couple hours ago:

The talk page is frequently edited and this bug has proven very annoying for
everyone involved with the article.
Comment 1 Brion Vibber 2005-10-28 10:20:42 UTC
This sounds similar to bug 3710. Does it still happen? Is it always the same version 
that it reverts to?
Comment 2 Owen Lloyd 2005-10-28 15:44:39 UTC
Actually, it hasn't happened since September 30th. Has something changed since
then? And yes, it always reverts to the same version.
Comment 3 Brion Vibber 2006-02-22 21:07:15 UTC
Assuming that whatever this may have been was fixed a billion years ago.

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