Template talk:Merged-to
Move to "Merged to"
editFollowing the new fashion and to be in line with {{Split to}} I suggest that this template is moved to {{Merged to}}. -- Magioladitis (talk) 08:28, 22 December 2013 (UTC)
Template-protected edit request on 27 July 2022
edit | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Please add |name = merged-to on a new line directly after the opening {{tmbox. This adds the box-merged-to class for use with bots and scripts. Chlod (say hi!) 12:08, 27 July 2022 (UTC)
Alternate wording needed
editThis template says "the content was merged into FOO and now redirects there". This is not accurate if the redirect is later turned into another article or even redirected somewhere else. Should there be a parameter to change the wording to drop the "now redirect there" part when not applicable. Or maybe just drop it entirely for simplicity. MB 03:21, 10 September 2022 (UTC)
- If the page is updated as you describe, I suggest replacing this template with the more general {{Copied}}. Per the lead of WP:Merging, both copying and redirecting are parts of the merge. Flatscan (talk) 04:24, 16 September 2022 (UTC)
- @Nihiltres, can you automate this? This template is used on article Talk Pages after a merger. Can you check if the article still redirects there and adjust the wording accordingly. The present wording is probably correct in the vast majority of the 16,000 transclusions. But I found one where the article was changed from a redirect to a dab page, and another where it was still a redirect but to a different target than at the time of the merge. As time goes on, "and now redirects there" will be wrong more often. MB 21:45, 20 September 2022 (UTC)
- Sure, it should be fairly simple combination of Module:Redirect and a conditional. What should the wording change to if the article no longer redirects to the specified target? Just remove the "and it now redirects there"? {{Nihiltres |talk |edits}} 22:09, 20 September 2022 (UTC)
- @Nihiltres, yes just drop it. The rest is still accurate. What happens if the target is different because of a move? In that case, the bot would have updated the target to avoid a double redirect but the redirect still goes to the place with the merged content. MB 22:33, 20 September 2022 (UTC)
Done. {{Nihiltres |talk |edits}} 21:01, 21 September 2022 (UTC)
- @Nihiltres, yes just drop it. The rest is still accurate. What happens if the target is different because of a move? In that case, the bot would have updated the target to avoid a double redirect but the redirect still goes to the place with the merged content. MB 22:33, 20 September 2022 (UTC)
- Sure, it should be fairly simple combination of Module:Redirect and a conditional. What should the wording change to if the article no longer redirects to the specified target? Just remove the "and it now redirects there"? {{Nihiltres |talk |edits}} 22:09, 20 September 2022 (UTC)
- @Nihiltres, can you automate this? This template is used on article Talk Pages after a merger. Can you check if the article still redirects there and adjust the wording accordingly. The present wording is probably correct in the vast majority of the 16,000 transclusions. But I found one where the article was changed from a redirect to a dab page, and another where it was still a redirect but to a different target than at the time of the merge. As time goes on, "and now redirects there" will be wrong more often. MB 21:45, 20 September 2022 (UTC)
Wording change
edit| | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Module:Copied (which feeds Template:Merged-from) has been updated to state the "content...was merged" after I complained that the previous wording "contents...was merged" was grammatically incorrect. Template:Merged-to should be changed to use the same wording "content...was merged" for consistency between these two often-paired templates. Changing Module:Copied to state "the contents...were merged" would have entailed additional coding complexity in the module. Bensci54 (talk) 16:35, 10 July 2025 (UTC)
- Done – Jonesey95 (talk) 16:53, 10 July 2025 (UTC)
Template-protected edit request on 2 August 2025
edit| | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
| − | For the contribution history and old versions of the merged | + | For the contribution history and old versions of the merged article, please see [{{fullurl:{{SUBJECTPAGENAME}}|action=history}} its history]. |
Sentence is clearer. FaviFake (talk) 09:39, 2 August 2025 (UTC)
Template-protected edit request on 5 August 2025
edit| | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
This template is currently using the wrong icon. The current icon 
is only used on templates placed on pages that are being merged into another or have already been merged into another (source pages). The correct icon to use is File:Mergefrom.svg 
, which is used in templates placed on the pages that are the destination of mergers. This would make it consistent with the templates {{merge from}} and {{Afd-merge from}} FaviFake.FaviFake (talk) 11:08, 5 August 2025 (UTC) FaviFake (talk) 11:18, 5 August 2025 (UTC)
- @FaviFake: {{Merged-to}} is in fact meant to be used on
source pages
, notdestination
pages. For destination pages, check {{Merged-from}}. Est. 2021 (talk · contribs) 19:39, 6 August 2025 (UTC)- Thanks! FaviFake (talk) 15:23, 8 August 2025 (UTC)