Skip to main content
replaced http://blog.stackoverflow.com with https://blog.stackoverflow.com
Source Link

A recent change introduced keeping merged questions around as stubskeeping merged questions around as stubs. I performed a couple of merges yesterday, and things appeared to be fine.

Today I ran across an old question migrated from Server Fault, and another copy that had been crossposted shortly afterwards. The Super User copy had been appended; the migrated copy was missing an owner. So I closed the migrated version as a duplicate, and then merged the migrated version into the crosspost.

After the migrated question was closed, it correctly showed the "migrated from" footer as well as the "closed by" footer. But after the merge, only the "migrated from" footer and the "closed by" footer are displayed; the merge footer is absent.

This particular question was closed-as-duplicate, so the auto-added "Possible duplicate" link in the question body still provides a link to the right question. But if this bug affects questions that are closed for other reasons, users will need to go to the question history to find the link to the new post.

A recent change introduced keeping merged questions around as stubs. I performed a couple of merges yesterday, and things appeared to be fine.

Today I ran across an old question migrated from Server Fault, and another copy that had been crossposted shortly afterwards. The Super User copy had been appended; the migrated copy was missing an owner. So I closed the migrated version as a duplicate, and then merged the migrated version into the crosspost.

After the migrated question was closed, it correctly showed the "migrated from" footer as well as the "closed by" footer. But after the merge, only the "migrated from" footer and the "closed by" footer are displayed; the merge footer is absent.

This particular question was closed-as-duplicate, so the auto-added "Possible duplicate" link in the question body still provides a link to the right question. But if this bug affects questions that are closed for other reasons, users will need to go to the question history to find the link to the new post.

A recent change introduced keeping merged questions around as stubs. I performed a couple of merges yesterday, and things appeared to be fine.

Today I ran across an old question migrated from Server Fault, and another copy that had been crossposted shortly afterwards. The Super User copy had been appended; the migrated copy was missing an owner. So I closed the migrated version as a duplicate, and then merged the migrated version into the crosspost.

After the migrated question was closed, it correctly showed the "migrated from" footer as well as the "closed by" footer. But after the merge, only the "migrated from" footer and the "closed by" footer are displayed; the merge footer is absent.

This particular question was closed-as-duplicate, so the auto-added "Possible duplicate" link in the question body still provides a link to the right question. But if this bug affects questions that are closed for other reasons, users will need to go to the question history to find the link to the new post.

replaced http://superuser.com/ with https://superuser.com/
Source Link

A recent change introduced keeping merged questions around as stubs. I performed a couple of merges yesterday, and things appeared to be fine.

Today I ran across an old question migrated from Server Fault, and another copy that had been crossposted shortly afterwards. The Super User copy had been appended; the migrated copy was missing an owner. So I closed the migrated version as a duplicate, and then merged the migrated versionthe migrated version into the crosspostthe crosspost.

After the migrated question was closed, it correctly showed the "migrated from" footer as well as the "closed by" footer. But after the merge, only the "migrated from" footer and the "closed by" footer are displayed; the merge footer is absent.

This particular question was closed-as-duplicate, so the auto-added "Possible duplicate" link in the question body still provides a link to the right question. But if this bug affects questions that are closed for other reasons, users will need to go to the question historyquestion history to find the link to the new post.

A recent change introduced keeping merged questions around as stubs. I performed a couple of merges yesterday, and things appeared to be fine.

Today I ran across an old question migrated from Server Fault, and another copy that had been crossposted shortly afterwards. The Super User copy had been appended; the migrated copy was missing an owner. So I closed the migrated version as a duplicate, and then merged the migrated version into the crosspost.

After the migrated question was closed, it correctly showed the "migrated from" footer as well as the "closed by" footer. But after the merge, only the "migrated from" footer and the "closed by" footer are displayed; the merge footer is absent.

This particular question was closed-as-duplicate, so the auto-added "Possible duplicate" link in the question body still provides a link to the right question. But if this bug affects questions that are closed for other reasons, users will need to go to the question history to find the link to the new post.

A recent change introduced keeping merged questions around as stubs. I performed a couple of merges yesterday, and things appeared to be fine.

Today I ran across an old question migrated from Server Fault, and another copy that had been crossposted shortly afterwards. The Super User copy had been appended; the migrated copy was missing an owner. So I closed the migrated version as a duplicate, and then merged the migrated version into the crosspost.

After the migrated question was closed, it correctly showed the "migrated from" footer as well as the "closed by" footer. But after the merge, only the "migrated from" footer and the "closed by" footer are displayed; the merge footer is absent.

This particular question was closed-as-duplicate, so the auto-added "Possible duplicate" link in the question body still provides a link to the right question. But if this bug affects questions that are closed for other reasons, users will need to go to the question history to find the link to the new post.

edited tags
Link
Jarrod Dixon
  • 38.4k
  • 4
  • 131
  • 162
edited tags
Link
Shog9 Mod
  • 454.3k
  • 203
  • 1.3k
  • 1.9k
Loading
Notice removed Canonical answer required by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Yoda pointed out a rather unfortunate interaction with the previous advice (and normal behavior) for merge stubs and the new effects of deletion on migrated questions: http://meta.stackoverflow.com/questions/35744/allow-diamond-moderators-to-reverse-question-migrations
Link
Shog9 Mod
  • 454.3k
  • 203
  • 1.3k
  • 1.9k
Loading
AFAIK, this was fixed.
Source Link
Shog9 Mod
  • 454.3k
  • 203
  • 1.3k
  • 1.9k
Loading
The missing "closed by" footer described in the original report has been fixed. Only the missing "merged with" footer remains (uh... missing)
Source Link
Shog9 Mod
  • 454.3k
  • 203
  • 1.3k
  • 1.9k
Loading
Notice added Canonical answer required by Gilles 'SO- stop being evil'
Bounty Started worth 50 reputation by Gilles 'SO- stop being evil'
edited tags
Link
Jeff Atwood
  • 311.4k
  • 107
  • 889
  • 1.3k
Loading
Source Link
quack quixote
  • 4.4k
  • 25
  • 32
Loading