Template talk:Copyvio

Archives

This page has archives. Sections older than 365 days may be automatically archived by .

Requested move 14 November 2023

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: Moved — Martin (MSGJ · talk) 12:37, 24 November 2023 (UTC)[reply]

Template:Copyvio/core → Template:Copyvio
Template:Copyvio → Deleted to make way for page move

– I added {{#invoke:unsubst}} functionality to this template, which will prefill the timestamp parameter. Since the "core" template fills the timestamp when substituted, the wrapper template is no longer needed. Awesome Aasim 15:44, 14 November 2023 (UTC)[reply]

Note: templates with non-redirected content, such as Template:Copyvio, are ineligible to be proposed titles in move requests unless they, too, are formally dispositioned. "Template:Copyvio → Deleted to make way for page move" has been added to this request to meet that requirement. If this is incorrect, please modify and be sure to factor in "bot considerations". P.I. Ellsworth , ed. ^{put'er there} 12:02, 15 November 2023 (UTC)[reply]

@Awesome Aasim - Just a procedural question here- the title you've proposed has non-redirecting content. For this request to actually be listed that template would also have to be moved. Do you have a proposed target for that? If so, could you add it to the template (WP:EXPLICIT). Or if the proposed target is just some sort of duplicate or the fulfill the same process, you can just list it as Deleted to make way for the move. I don't really know how the templates side of this works, but I do know that the way this is proposed currently is causing a minor problem with the bots on the RM side. estar8806 (talk) ★ 01:40, 15 November 2023 (UTC)[reply]

I have made a post at WP:VPT to see if someone with technical expertise can have a look at this. On the face of it, I worry that moving as proposed which would involve deleting a template that has existed since 2004 will cause some sort of issue but every chance I'm wrong. Jenks24 (talk) 08:34, 24 November 2023 (UTC)[reply]
I just tested it and seems to work okay. The only issue I am seeing is the HTML comment which is at the top of /core is now being pasted onto articles, (see [1]). @Awesome Aasim can you comment on whether this was intentional? — Martin (MSGJ · talk) 10:41, 24 November 2023 (UTC)[reply]
@MSGJ, I moved the comment into the wrapper and it works fine with substitution now, see here. NmWTfs85lXusaybq (talk) 11:40, 24 November 2023 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Wording change aimed at avoiding lint errors

Not including {{copyvio/bottom}} causes missing end tag lint errors. This hasn't really been an issue thus far, as this error category is considered low priority and copyright issues would generally get cleaned up way before anyone would get to fixing the lint errors caused by them. However, since all higher priority lint error categories have been cleaned up in mainspace, this is starting to change. Although there are still 70,000+ unfixed errors, the ones involving tags with higher disruptive potential for layout – like <table> and <div> – are very close to being eliminated with only ~1000 errors left, dropping daily by ~100. Which means the {{copyvio}} lint errors are starting to surface, so helping to avoid them has become something to address. Gamapamani (talk) 09:33, 23 June 2024 (UTC)[reply]

The template used to close itself properly without any need to manually add a </div> or anything. That functionality seems to have been removed in the overhaul of the template. Can it be restored, please? I mean, if the template is causing an error, let's stop it from doing so, not change the wording, right? Justlettersandnumbers (talk) 11:15, 4 July 2024 (UTC)[reply]

I'm all for bringing back that functionality if it existed previously. I have no involvement with this template or it's subject matter other than fixing the lint errors caused by it, so I addressed that part. Gamapamani (talk) 11:34, 4 July 2024 (UTC)[reply]

Jonesey95, it looks as if you might understand what's needed to fix this. Could you kindly take a look? Many thanks, Justlettersandnumbers (talk) 18:29, 14 August 2024 (UTC)[reply]

My understanding is that the template leaves the div tag open so that it essentially blanks the whole page, displaying the template instead of displaying any potentially copyvio text or images on the page. If editors follow the documented recommendation to place the /bottom template at the bottom of the page, there should not be any Linter errors caused by this template. My recommendation is to treat the copyvio template like {{div col}} or {{collapse top}} or any "xxx start" table template, or any unclosed italic or bold markup: if the corresponding end tag or markup is missing, that's an error that should be corrected by adding the missing end tag or markup. Add the missing markup and keep moving. – Jonesey95 (talk) 18:35, 14 August 2024 (UTC)[reply]

@Justlettersandnumbers TBH, while I continue to agree that it'd be great if inserting just the top {{copyvio}} did the trick without needing to place anything at the bottom, I don't really understand what the big deal is with having to put {{copyvio/bottom}} there, like people routinely do with other start/end type templates mentioned by @Jonesey95. It only takes a couple of seconds, surely not a huge effort relative to the entirety of a copyright investigation, or a hurdle discouraging anyone from filing a report? (Maybe my thinking is unusual in some way, because I also don't get people who have the time and ability to track down a violation, but then for some reason can't properly mark the section they're reporting and hide the entire page instead...)

Now that I think about it: are you sure there was a time when this template used to auto-close? It's not that I doubt your word, I just think you could be mistaken in the sense that you've interpreted the absence of any reaction to these lint errors in the past as the absence of the errors themselves. I think if an auto-closing version existed in the past and you/someone can track it down from the history, it should be possible to employ the same method again (unless it's dependent on something that has since changed in Mediawiki software).

Gamapamani (talk) 07:58, 15 August 2024 (UTC)[reply]

I don't really understand what the big deal is with having to put {{copyvio/bottom}} there - A lot of us copyright problems regulars are using a script, and we used to only use the bottom template when we were partial blanking. Part habit and part using convenient scripts to speed up a purely manual area of Wikipedia. @Chlod, think it's possible to make Infringement Assistant put copyvio/bottom when blanking the full page? Sennecaster (Chat) 01:34, 2 September 2024 (UTC)[reply]

Definitely possible; it should be a quick fix. I'll work on it sometime today. Chlod (say hi!) 03:43, 2 September 2024 (UTC)[reply]

This change was deployed today. I've also added a configuration value for it in case it can be disabled in the future, which will make it easy to apply the change instantly to all users of Deputy. Chlod (say hi!) 16:40, 4 September 2024 (UTC)[reply]