Template talk:New page DYM

Protected edit request on 1 April 2022

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

Hi there! Could the sandbox be copied over to the main page, please? It implements suggestions for removing a forwards-slash (/) or backwards-slash (\) from the end of the page title. This is common in typos in links, and also as generally on the Web URLs can have a slash on the end, but not on Wikipedia (MediaWiki considers it a different page altogether). Thanks! 🐶 EpicPupper ^{(he/him | talk)} 18:51, 1 April 2022 (UTC)[reply]

Done Good idea. Galobtter (pingó mió) 22:27, 5 May 2022 (UTC)[reply]

User (talk) space

Currently this will generate links in userspace and user talk space as well, if the current visited title does not exist but a version of the title that this template checks for does; in userspace, that often means that there is not a registered account with the current name, but there is one with the "corrected" name, which should generally be fine. However, it may sometimes be the case that there is an account with the current name, and also one with the corrected one, and in that case this message should probably not be displayed (especially since it may be the case that the current-named account is a good-faith contributor, whereas the suggested account is some flavor of blocked vandal, sockpuppet, impersonator, etc.) But I don't know if it's possible to check for whether an account with a given name exists from within wikitext (or even from within a module, for that matter); my first thought was GENDER, but that seems to always return the gender-neutral option if the input doesn't correspond to a registered account. So unless someone knows how to detect an account's registered status in this way, it might be better for this template to do nothing (or only the bare minimum, e.g. soft hyphen-stripping) in userspace. 「ディノ奴千？！」^{☎ Dinoguy1000} 09:34, 15 August 2022 (UTC)[reply]

IMO it's okay for the template to suggest corrected titles in user space; it can be helpful in the case of typos etc, and there's little chance of confusion caused by its corrections (trailing slash, etc). EpicPupper (talk) 02:30, 12 April 2023 (UTC)[reply]

This isn't about suggesting corrections in userspace in general (which is fine), but in the specific case where the "correction" is to the base page name, which can (and sometimes will) correspond to a different user account (including, in some cases, accounts which have been blocked, banned, glocked, etc).

It's probably best for this template to not attempt correcting base page names in userspace at all, but that is probably too annoying to implement unless this template is either split into a wrapper which does parameter preprocessing and core which handles the actual logic, or converted to a module (with preference to the latter, if anyone wants to take the initiative). 「ディノ奴千？！」^{☎ Dinoguy1000} 09:54, 8 July 2023 (UTC)[reply]

Protected edit request on 24 April 2023

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

I request adding support for checking if the page exists with backslashes removed, per the recent proposal I have made at village pump: such page views can come from sites with faulty Markdown systems that needlessly escape underscores in links, which has shown to already attract hundreds of views to a particular redirect. Taking the soft hyphen code as an example, this should consist of adding the following:

{{ #ifeq: {{FULLPAGENAME}} | {{#invoke:String|replace|source={{FULLPAGENAME}}|\}}
 || {{ #ifexist: {{#invoke:String|replace|source={{FULLPAGENAME}}|\}}<!-- page exists without backslash(es) -->
  | {{Did you mean/box|{{#invoke:String|replace|source={{FULLPAGENAME}}|\}}}}
 }}
}}

Randi Moth ^Talk_Contribs 18:54, 24 April 2023 (UTC)[reply]

LGTM. Frostly (talk) 22:51, 24 April 2023 (UTC)[reply]

Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. — JJMC89 (T·C) 04:12, 4 May 2023 (UTC)[reply]

@Randi Moth courtesy ping! Frostly (talk) 01:02, 5 May 2023 (UTC)[reply]

Thank you for the ping. @JJMC89: I have changed the example, and it seems to be working fine with the test cases. The {{FULLPAGENAME}} had to be changed (I picked a positional argument of {{{1}}}) to be able to test it since the preview doesn't allow you to select a non-existing page. {{{1}}} will have to be changed back to {{FULLPAGENAME}} in the main template. Randi Moth ^Talk_Contribs 13:09, 5 May 2023 (UTC)[reply]

@Randi Moth: I changed the positional parameter out for a proper demo parameter that falls back to {{FULLPAGENAME}} so that the sandbox code can be copied directly to the live template without modification. The testcases look good, though I note that they don't have complete coveerage of the replacements this template performs (though that's tricky given the number of #ifexist this template uses to do so). If you don't have any concerns that popped up between your last comment here and now, I can fulfill this edit request. 「ディノ奴千？！」^{☎ Dinoguy1000} 04:49, 18 June 2023 (UTC)[reply]

Done Izno (talk) 21:58, 5 July 2023 (UTC)[reply]