Template talk:Copied

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.

Copied pages:
Copied Template:Copied (oldid, history) → th:แม่แบบ:Copied (diff) Copied Template:Copied (oldid, history) → incubator:Template:Wp/nod/copied (diff) Copied Module:Copied (oldid, history) → incubator:Module:Wp/nod/Copied (diff) Copied Module:Copied (oldid, history) → th:มอดูล:Copied (diff)

Archives

Archive 1

This page has archives. Sections older than 90 days may be automatically archived by when more than 4 sections are present.

Clarify where the template should go

Clarify if this template should go in the main article or the talk page. I think this is meant to be used in the talk page but it isn't very clear. I see at least one example of an article that used it in the main page see Chivalry Bookshelf. There is this line but it is not explicit enough in my opinion: "Adding this template on the talk page is not a substitute for attribution in the page history using edit summaries." J2UDY7r00CRjH (talk) 20:27, 18 July 2024 (UTC)[reply]

Merged-from nesting

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

A previous template was made by Flatscan at the request of Otherlleft - now deleted, with reasoning of being 'redundant' with this template - to act as a nested version of {Merged-from}.

For this reason, I propose to change the default value of the to parameter to the article {Copied} is invoked on. Additionally/as a result, to should not need to be specified for each from1, from2, etc.. This way, the template would act easier as a nested version of {Merged-from}. It might also be accompanied by a stylistic change - such as removing the ambiguity of 'to or from' in the displayed tag.

As an example, see the {copied} tag at Talk:Customer relationship management. Tule-hog (talk) 02:26, 25 July 2024 (UTC)[reply]

Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. —⁠andrybak (talk) 14:27, 4 August 2024 (UTC)[reply]

Request is in 'change... to...' format, so I am assuming it is only the full meaning thats unclear.

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.

Copied merged-from (history) → copied
Copied other (history) → copied
Copied example (history) → copied

Observe {copied} requires values for to1, to2, and to3. I propose (if possible) to automatically use the ARTICLENAME of the page the template is called on as either all the to or from values, when only the other type of values are provided. For example, if I only specify (to1, to2, to3), ARTICLENAME should be automatically assigned to (from1, from2, from3) - similarly in the reverse case. Tule-hog (talk) 15:14, 4 August 2024 (UTC)[reply]

No redirect from

This edit request has been answered. Set the |answered= or |ans= 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)[reply]

Done Sohom (talk) 04:52, 5 September 2024 (UTC)[reply]

Bug with numbered parameters

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. Use from instead of from1.
Script warning: from_oldid is not a row-based parameter. Use from_oldid instead of from_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)[reply]

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)[reply]