Template talk:User sandbox+

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Pppery (talk | contribs) at 21:36, 6 March 2018 (→‎Re-structure naming: Re). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Requested move 5 March 2018

– Template organization; these are only used directly on Template:Article page template class/Article template library, which itself is connected to the {{Article page template}} family. {{3x|p}}ery (talk) 00:19, 5 March 2018 (UTC)[reply]

@ManosHacker: {{3x|p}}ery (talk) 00:20, 5 March 2018 (UTC)[reply]

There is coding inside that creates the paths of templates to be called. They are not called directly. As some templates do not seem to be linked to each other, moving them to different names breaks functionality.   ManosHacker talk 00:32, 5 March 2018 (UTC)[reply]

Could you please explain that further? {{3x|p}}ery (talk) 00:40, 5 March 2018 (UTC)[reply]
The central template is self-adaptive to where it resides (user space or main space, for example) and behaves differently. It behaves differently when the page does not exist yet and also if it has been created in user space or main space, no matter where it currently resides. On top of these, things appear or hide or display different messages or different functionality is enabled. There are nesting limitations in template code that do not allow to do everything programmatically, so I have three different templates that are almost identical: Template:Custom page template (user),Template:Custom_page_template_(program) and Template:Create_sandbox_subpage_item in the fear of crossing the limit. I welcome you to change of naming, I also wish for a more compact code.   ManosHacker talk 00:58, 5 March 2018 (UTC)[reply]
And this means that these specific templates can't be moved because ... As fair as I can tell, the name of these templates is not determined progamatically. {{3x|p}}ery (talk) 01:18, 5 March 2018 (UTC)[reply]
There is an Editnotice regarding delayed safesubst that is only to appear in Article page templates edits, not assistive templates under the same name.   ManosHacker talk 02:25, 5 March 2018 (UTC)[reply]

Regarding [Template:Article page template class/Article template library], libraries are being created by declaring them (as classes), and all belong in the same template space. This is "Template:Article page template class" for the time being. A better name for this space is welcome. Please avoid Etitnotice conflict here, too.   ManosHacker talk 06:36, 5 March 2018 (UTC)[reply]

Editnotice conflict can be avoided by using plural, i.e. "Article page templates" instead of 'Article page template".   ManosHacker talk 08:07, 5 March 2018 (UTC)[reply]

Sorry, but that defeats the point of this requested move, which is to arrange these internal templates as subpages of their base templa tes, and some having a "s" at the end doesn't do that. {{3x|p}}ery (talk) 15:43, 5 March 2018 (UTC)[reply]
Editnotice conflict has a solution. By wrappping editnotice between {{#ifeq: {{PAGENAME}} | {{BASEPAGENAME}} | and }}, the templates names proposed above do not get the editnotice. If implemented this way (or any similar way like titleparts), the naming of the two templates proposed (not global library itself move) is fine for me.   ManosHacker talk 20:23, 5 March 2018 (UTC)[reply]

Re-structure naming

Assistive templates

Optical help

Sandbox



Article page templates




Group Template Editnotice

How about this structure? Is plural more accurate? Files are the same (renamed) and two of them are merged into one.   ManosHacker talk 17:40, 6 March 2018 (UTC)[reply]

It's not clear to me what corresponds to what in the format you've provided. {{3x|p}}ery (talk) 21:36, 6 March 2018 (UTC)[reply]