3

Possible Duplicate:
Closed-then-merged question missing “closed by” and “merged to” footers

We have had some crossposting between cs.SE and math.SE and solved the issue(s) by migrating to one site, closing one of them and merging it into the other.

Now the question list looks like this for me (moderator):

enter image description here

And the closed/migrated question:

enter image description here

There is no indication whatsoever that the closed question has been merged somewhere (and where it has been merged to). Not logged-in users (and non-mods resp. low-rep users, I assume) do not see the closed/merged question and are forwarded to the merge target when they try to visit the closed question.

Please label merged questions as such (maybe just like deleted ones?) and show the merge target.

Improve this question
11
  • @Raphael: Perhaps all you really need to do is delete it? The revision history says it's been merged and locked, just not deleted.
    – animuson StaffMod
    Commented May 18, 2012 at 1:33
  • @animuson: It is not clear to me that/why I should have to do this (normal users don't see the question!). All in all, the merge function seems to be broken, given that I have to close and delete manually.
    – Raphael
    Commented May 18, 2012 at 1:34
  • @Raphael: Normal users do see the question. I logged in, I clicked that question, it shows perfectly fine to me as a closed question. It's only not-logged-in users who are getting redirected. I don't know how moderator tools work, but normally merged questions are also deleted. If it's supposed to be automatic, this is a bug.
    – animuson StaffMod
    Commented May 18, 2012 at 1:36
  • @animuson: Huh, weird. Why would logged-in users be treated differently? And where would they be sent if I deleted the question?
    – Raphael
    Commented May 18, 2012 at 1:40
  • Wow, tons of misinformation in the comments here. Deleting with abandon. This is a case of footer overflow - there's simply no support for stacking merged, closed, and migrated footers on a single question.
    – Shog9 Mod
    Commented May 18, 2012 at 3:28
  • @Shog9: This question may be a duplicate, technically, but the linked one has not been answererd/acted upon then, imho. Jeff's answer is not satisfactory; why would I have to manually delete?
    – Raphael
    Commented May 18, 2012 at 7:41
  • @Raphael: the stub will be deleted automatically after a while regardless - deleting it manually just removes the confusion sooner. Yeah, this should really be fixed, but it's sort of an edge-case.
    – Shog9 Mod
    Commented May 18, 2012 at 7:44
  • @Shog9: So how do we keep this a current issue for the devs? Do they consider closed questions? Should I open a new question asking for changes to the merge function? (By the way, there are enough edge cases in the mod tools to be annoying, but that's for another day.)
    – Raphael
    Commented May 18, 2012 at 7:47
  • You might add an answer to the question I linked, if you have something to say that's not covered there now. Old questions aren't forgotten about, this simply isn't something that's happened enough to warrant the effort it would take to fix right now (FWIW, there's a different work around that doesn't involve deletion, but deletion is slightly less confusing than clearing the migration history).
    – Shog9 Mod
    Commented May 18, 2012 at 7:55
  • @Shog9: I did so, although status-bydesign looks forbidding.
    – Raphael
    Commented May 18, 2012 at 8:12
  • Future visitors, note that discussion lead to not deleting the stubs. See there for details.
    – Raphael
    Commented Jun 3, 2012 at 21:20

0

Reset to default