Last modified: 2014-07-02 16:53:42 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 T56873, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54873 - "The revision you have selected is corrupt, and cannot be viewed" or "The thread you specified does not exist"
"The revision you have selected is corrupt, and cannot be viewed" or "The thr...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
https://www.mediawiki.org/w/index.php...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-02 13:42 UTC by Wikifram@gmail.com (Account disabled)
Modified: 2014-07-02 16:53 UTC (History)
5 users (show)

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


Attachments

Description Wikifram@gmail.com (Account disabled) 2013-10-02 13:42:17 UTC
As described [https://www.mediawiki.org/w/index.php?title=Project_talk:Current_issues&oldid=794412 here]; in a fairly lengthy Liquidthreads discussion, the most recent replies are no longer correctly added to the "history", and clicking on the revision time in the "history" gives the error: "The revision you have selected is corrupt, and cannot be viewed". Adding new repiies doesn't change the starting point of the error.
Comment 1 Andre Klapper 2013-10-02 14:47:58 UTC
Also see bug 47006 comment 4
Comment 2 Durga 2014-01-13 12:49:01 UTC
I am interested in working on this bug, could someone please assign it to me?
Comment 3 Andre Klapper 2014-01-13 13:03:03 UTC
Feel free to just work on it (no real need for assignment). Thanks for your interest!
Comment 4 Andre Klapper 2014-03-19 14:23:58 UTC
Durga: Any news to share here? Are you still working on this?
Comment 5 Andre Klapper 2014-07-02 16:53:42 UTC
Durga: I am resetting the assignee of this issue to default because there has been no progress in the last months. Feel free to take it again when you are actually planning to fix this. Thanks.

(Decreasing severity as I don't see dataloss here.)

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


Navigation
Links