Last modified: 2009-06-26 12:31:29 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 T17410, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15410 - deleting Thread:Image:foo.jpg_(1) appears to have also deleted Thread:foo.jpg_(1)
deleting Thread:Image:foo.jpg_(1) appears to have also deleted Thread:foo.jpg...
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Andrew Garrett
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-01 03:38 UTC by Jim Tittsler
Modified: 2009-06-26 12:31 UTC (History)
1 user (show)

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


Attachments

Description Jim Tittsler 2008-09-01 03:38:53 UTC
A user started a thread on Image:foo.jpg_(1), and later started a replacement thread on my talk page titled foo.jpg_(1).  He asked that the original be deleted.  When I deleted Image:foo.jpg_(1) the foo.jpg_(1) thread (including all its children) from my talk page appears to have also disappeared (and does not appear in the deletion log).  I suspect there is something odd in the handling of the "Image:" prefix of the original.
Comment 1 Jim Tittsler 2008-09-01 03:46:51 UTC
By visiting the URL of one of the posts in the missing thread directly, the web server error log says:

[Mon Sep 01 05:40:24 2008] [error] PHP Fatal error:  Call to a member function root() on a non-object in /usr/local/mw-svn/extensions/LiquidThreads/LqtBaseView.php on line 384
Comment 2 David McCabe 2008-12-27 05:52:02 UTC
Please give steps to reproduce.

Was the thread moved from one page to another, or were they completely separate threads?
Comment 3 Andrew Garrett 2009-06-26 12:31:29 UTC
Unable to reproduce, and the offending code has been reimplemented. Assuming this was fixed.

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


Navigation
Links