Last modified: 2011-07-04 20:01:18 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 T26179, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24179 - Moving thread from FOO -> BAR -> FOO yields a duplicate making moving of posts is impossible to (undo)
Moving thread from FOO -> BAR -> FOO yields a duplicate making moving of post...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 25033 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-29 14:24 UTC by Ævar Arnfjörð Bjarmason
Modified: 2011-07-04 20:01 UTC (History)
4 users (show)

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


Attachments

Description Ævar Arnfjörð Bjarmason 2010-06-29 14:24:22 UTC
Related to bug 24178, when you move a thread from FOO -> BAR you get a redirect on FOO, so your forum on FOO will be:

   = My thread
   Moved to BAR blah blah

But and on BAR:

   = My thread
   The original content

However, if you then decide to change your mind and move "My thread" back from BAR -> FOO you end up with this:

   = My thread
   The original content
   = My thread
   Moved to BAR blah blah

I.e. there are now 2 threads under the same name, the now-broken redirect and the original.
Comment 1 Brandon Harris 2010-09-09 19:02:04 UTC
If we can get this done before redesign work, that would be good.  If not, we need to solve for it, but I'm okay with this going into next phase.
Comment 2 Nemo 2011-07-04 20:00:46 UTC
*** Bug 25033 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