![]() | This template was considered for merging with Template:Merged-from on 12 March 2025. The result of the discussion was "keep". |
![]() | Template:Copied is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
![]() | Text has been copied to or from this page; see the list below. The source pages now serve to provide attribution for the content in the destination pages and must not be deleted as long as the copies exist. For attribution and to access older versions of the copied text, please see the history links below.
|
|
|
This page has archives. Sections older than 90 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Add an option for the `from` argument to be a {{no redirect}}
link.
Useful in cases where the 'from' article is now a redirect, since it is the history of that page that is of interest - not the article it redirects to. Tule-hog (talk) 19:18, 2 September 2024 (UTC)
Despite:
local from_oldid = args["from_oldid"] or args["from_oldid1"] or "" local from = args["from"] or args["from1"] or ""
in the module, neither |from=
nor |from_oldid1=
are working, and they throw errors:
Script warning:
from
is not a row-based parameter. Usefrom
instead offrom1
.
Script warning:from_oldid
is not a row-based parameter. Usefrom_oldid
instead offrom_oldid1
.
This is against the intent of the code, and makes it confusingly inconsistent. Same problem is also affecting {{Split article}}
and maybe some other templates in this class. — SMcCandlish ☏ ¢ 😼 04:47, 23 December 2024 (UTC)
PS: |from2=
is also failing in this template (probably along with other numbered params), so it's even less consistent with the other templates, and is mandatorily used as a complete template multiple times if multiple copying events must be recorded. This is "suboptimal". — SMcCandlish ☏ ¢ 😼 04:56, 23 December 2024 (UTC)
![]() | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Add {{check talk |nocat={{{nocat|}}}}}
to the beginning of the template, to make sure it is placed correctly (nocat
allows for testing). Tule-hog (talk) 02:34, 2 April 2025 (UTC)
![]() | This edit request to Module:Copied has been answered. Set the |answered= parameter to no to reactivate your request. |
I have made some modifications to the module so as to invoke it from {{merged-from}}
(for reasons detailed at request link in the hatnote).
The only change that should affect normal {{Copied}}
usage is the to
parameters will now default to the page the template is invoked on (I previously requested this at #Merged-from nesting). I have also added talk
parameters which link to the from
s' talk pages, it defaults off (so no change unless explicitly desired).
Other than those modifications, the rest are basically aesthetic to match the language of the current {{merged-from}}
(they only apply when invoked from the rewritten merged-from - I use a meta-parameter mergedFrom
which shouldn't be used manually). (I also distinguished Category:Wikipedia pages using merged-from template without oldid, which might be unnecessary.) Tule-hog (talk) 03:42, 2 April 2025 (UTC)
{{merged-from}}
is for completed merges (note merged-from is the target of {{merged}}
, so usable on source pages as well as destinations; however, use on a source page requires explicitly setting to & from, since 'to' defaults to the transcluding page).