Template talk:Please see

Subst
This template has to be Subst'ed because of the use of a section heading. Is there a better way to do this without having to Subst it?—Markles 14:21, 28 July 2008 (UTC)
 * Because it's meant for the user talk namespace, I think it should always be subst'ed. Why?  Because that way, even if the template gets edited later, the original notice stays exactly as-is, providing an accurate record of what the editor saw on their talk page.  If we don't subst it, and then later it gets edited, or even deleted, the user's talk page is no longer an accurate reflection of the conversation.--Aervanath lives in the Orphanage 14:52, 28 July 2008 (UTC)
 * Good point.—Markles 15:19, 28 July 2008 (UTC)
 * Not really., , etc. are rarely subst'd, and don't demand in their documentation that they be subst'd. It's different for user warning templates, where because user warnings and what they said can be facts with serious consequences, you do definitely wanted to subst them.  While this particular template does have to be subst'd because it embeds section heading and signature, the rest of the rationale for doing so doesn't apply, and a variant of this template that did not embed these things, like  doesn't, would not be subst'd. — SMcCandlish   Talk⇒ ʕ(Õلō)ˀ  Contribs. 09:55, 3 December 2011 (UTC)

Name change
I greatly welcome a better name. (It's currently Please see.) I suggest "See discussion." Any other nominations?—Markles 14:22, 28 July 2008 (UTC)
 * I've created "See discussion" as a redirect to "Please see". I prefer the current name because it's shorter.  Either way, we can't move it until the Tfd is over.--Aervanath lives in the Orphanage 14:55, 28 July 2008 (UTC)

tfd removed and a recommendation
I have removed the tfd. Is there any chance of having the signature as part of the template rather than having to add it manually? Some editors may forget to add it. -- Alan Liefting (talk) - 20:42, 28 July 2008 (UTC)
 * I've experimented with that, but was never able to get it right. Which templates have built-in signatures?  I can go look and copy them.--Aervanath lives in the Orphanage 21:02, 28 July 2008 (UTC)
 * ✅ Figured it out.--Aervanath lives in the Orphanage 07:12, 5 August 2008 (UTC)

Friendliness
I reverted an edit changing the template from "You might be interested in..." to "Please see". I think "Please see" sounds more like a command, and this template isn't for something obligatory, it's for letting people know, in a friendly fashion, of a discussion that they might be interested in.--Aervanath lives in the Orphanage 05:50, 19 November 2008 (UTC)

Minor change
In case anyone was wondering about these edits, what I was doing was substing the parser functions so that section edit links would show up (before, if you used this on a talk page, you would not get edit links next to the section). It should be working now. r ʨ anaɢ talk/contribs 13:11, 8 April 2009 (UTC)

Personalisation
I've been using this for messages from  our project. The main point  is that  it  personalises the message (where it  says 'Please see' below that  is the name of the name space, which would be the user's name). I think it sounds nice and polite. The only thing  it  doesn't do  is automate the signature (the signature on  it  is mine). I don't know how to  make it  into  a template:

Hi ! An article you have been involved with has been tagged by its parent project as being in need of a little attention or further development. If you can help with these minor issues please see talk:xxxxxx--Kudpung (talk) 01:29, 19 June 2009 (UTC)

Wikipedia talk:WikiProject Norway#Category:People by district in Norway
You are invited to join the discussion at Wikipedia talk:WikiProject Norway. meco (talk) 23:46, 24 January 2011 (UTC) (Using ). __meco (talk) 23:46, 24 January 2011 (UTC)


 * The above is merely an example to show that there is something very wrong with this template. The code used to produce this was  __meco (talk) 23:48, 24 January 2011 (UTC)
 * It seems like it's working fine. I think the problem is that you included "~" .  That's already included in the code.  I can add some explanation in the instructions telling users not to include that.  Am I right about the problem, and do you think it would help? 01:03, 25 January 2011 (UTC)
 * Yes, I think that should be included. Also, it is customary that such templates do not identify themselves overtly but keep the self-reference hidden as a commented out text. __meco (talk) 11:35, 25 January 2011 (UTC)
 * I'll put a note on the usage to tell users not to add "~" . The template's self-id, however, is included because it's a subst'd template and there's no other way to let future users know how it was employed.  It's only used on talk pages, so it's not that intrusive.  I tried to make it as small in conspicuous as possible, and I've reduced it to pls (although I welcome suggestions on reducing its footprint further). —Markles  13:15, 25 January 2011 (UTC)

Rendering problem
Hi.

Special attention for. Revision #644940455, currently in the sandbox renders as follows:

This code:
 * Mobile operating systems

...gives: You are invited to join the discussion at Mobile operating systems&. Thanks. Codename Lisa (talk) 08:01, 1 February 2015 (UTC)

Best regards, Codename Lisa (talk) 08:05, 1 February 2015 (UTC)
 * This code:


 * ...gives:

You are invited to join the discussion at Mobile operating systems&. Thanks. —  15:19, 1 February 2015 (UTC)


 * , I apologize if you thought I was rude or DICKish. I literately spent an hour or so digging through all of your recent talk contributions and could find no instances of it being broken or you fixing a broken usage or even discussing it with another editor and your edit summary was less than helpful Faulty rendering. Reverting to last known good state.  Anyways, I've fixed the rendering issue per this section and have put it back into the live template so that my uses with a link directly to a section aren't broken.  Thanks and happy editing. —   15:19, 1 February 2015 (UTC)


 * No, I didn't get to thinking the Dictator part; I honestly ... forgot! But you should have asked me. I won't bite! (Especially not you.) So when I forget to take the initiative, please start the discussion part. Remember how we TemplateEditors work? Upon encountering technical faults, we revert and stick to discussion and WP:1RR until the technical difficulty is resolved. There is no other safe way. Also, I had to delete the heading in your message; it prevents me from replying. (I am sure there was a dummy heading template that simulated it but don't remember its name.)


 * Best regards,
 * Codename Lisa (talk) 17:31, 1 February 2015 (UTC)

Forced italics?
My explanation in the es was pretty complete, but I want to expand a little on the italics part. I don't see a reason to force that text to always be italics. It isn't that difficult if someone wants their text to be italic to wrap it in. It's only four characters after all (even if we made in an optional parameter with a minimum number of characters it would be y which is also four characters, so there is no savings there. Also, by forcing italics in this way, if someone wanted the text to be bold only it would require them to input it as 'Some bold text' or if they wanted to use a single quote to wrap their text they would have to use 'single quoted text'.  All of these pieces means that it is a bad idea to force italics in this way (or any way for that matter). —   14:56, 15 April 2015 (UTC)
 * I understood your reason, and if no one wants it I'll leave it alone. The only reason I had changed it is because I used Twinkle to send this to someone and was surprised when it didn't italic my comment like twinkle does with other user talk messages when added to templates. I guess I could contact the twinkle people about it, but I though this would just be simpler. I also think you miss-layered the code and nowiki above. EoRdE6(Come Talk to Me!) 15:08, 15 April 2015 (UTC)
 * You could add it in a pull request on GitHub for Twinkle. It would actually be a very easy thing to do.  If coding .js isn't something you want to think about, I think a request/discussion on WT:TW asking for it would certainly be useful.  You are right about the mislayering, I do it ALL the time and as such I really wish that  or someone would do this request soon. —   15:16, 15 April 2015 (UTC)

Fish Eye
has raised concern about the fish eye image. Is there a more appropriate image that can be used?--RightCowLeftCoast (talk) 00:55, 13 June 2015 (UTC)
 * Yes, and besides my initial comment you have linked, it also triggers a reflex that malware might be on Wikipedia. Please, please use an image that doesn't look like an invasion of privacy.  Thanks so much. — Maile  (talk) 12:10, 13 June 2015 (UTC)


 * NOTE I've updated the template to optionally turn off the image by using  -- 70.51.202.183 (talk) 04:36, 14 June 2015 (UTC)

Template-protected edit request in re Template:format linkr
This template doesn't handle underscores right. It is quite normal for power users to want to use underscores with this template, as it's faster. (E.g. @ .)

I have updated it to use  instead. (based off latest rev., 957158492) Please therefore copy Template:Please see/sandbox to Template:Please see. Psiĥedelisto (talk • contribs) please always ping! 12:58, 25 June 2020 (UTC)
 * As the user guilty of providing the example material here, I'd be very happy to see this change, assuming it works as intended. Are there any articles that include an underscore in the title that might create issues? &#123;{u&#124; Sdkb  }&#125;  talk 18:18, 25 June 2020 (UTC)
 * Such cases should be by far in the minority. And, since this template is substituted, we don't have to worry about old uses of it, only new ones. In any event, I just added a y which switches between  and  . Once it's in the main template I'll document it in Template:/doc. Psiĥedelisto (talk • contribs) please always ping! 18:29, 25 June 2020 (UTC)
 * Maybe I'm missing something, but what is "not right" about the above examples? Primefac (talk) 19:28, 30 June 2020 (UTC)
 * They have underscores, when they would look better without them. Psiĥedelisto (talk • contribs) please always ping! 19:30, 30 June 2020 (UTC)
 * Red information icon with gradient background.svg Not done for now: please establish a consensus for this alteration before using the template. Nardog (talk) 23:31, 1 July 2020 (UTC)
 * I'm not seeing anyone oppose, so keeping open. &#123;{u&#124; Sdkb  }&#125;  talk 23:50, 1 July 2020 (UTC)
 * Well, please don't do that. A request for establishing a consensus should be taken as a form of opposition.
 * A problem I see with Format linkr is that it would leave template code in the section title, which would ruin the section link in summaries (see e.g. ). I'll see if we could use safesubst. Nardog (talk) 00:04, 2 July 2020 (UTC)
 * Fixed said problem in /sandbox. Reactivate it if you want. I prefer to let another editor review it instead of rolling it out myself. ( Btw, please do not use  as it's deprecated. See WP:HTML5 for alternatives—there are also tlx, tltt, etc.) Nardog (talk) 00:52, 2 July 2020 (UTC)
 * Okay, reactivated Psiĥedelisto (talk • contribs) please always ping! 02:25, 2 July 2020 (UTC)
 * Yes check.svg Done Mdaniels5757 (talk) 19:46, 26 July 2020 (UTC)

Fish eye image
Following up from the discussion above, the current image, File:Farm-Fresh_eye.png, is overly skeumorphic and thus seems outdated. I'd suggest switching to File:Symbol watching blue lashes.svg, so that we'd have instead of. Thoughts? &#123;{u&#124; Sdkb  }&#125;  talk 22:21, 20 July 2020 (UTC)
 * Courtesy pings  &#123;{u&#124;  Sdkb  }&#125;  talk 22:22, 20 July 2020 (UTC)
 * Thanks for the ping. I am neither opposed or supportive of it. Please see is more of a FYI or request additional editors attention. So I can see having the eye for the see aspect, but would be OK with another symbol that maybe suggested.-- RightCow LeftCoast ( Moo ) 01:05, 22 July 2020 (UTC)
 * Why not a simple Echo chat icon.svg? Psiĥedelisto (talk • contribs) please always ping! 17:50, 25 July 2020 (UTC)
 * , since the template will be going on talk pages, I'm not sure having a talk symbol would add any visual information. The eye at least connotes a specific type of talk page post. &#123;{u&#124; Sdkb  }&#125;  talk 22:04, 28 July 2020 (UTC)
 * Hmm. What about Mail-message-new.svg or Nuvola_apps_edu_languages.svg? Psiĥedelisto (talk • contribs) please always ping! 22:06, 28 July 2020 (UTC)
 * , hmm, it's nice to have several options to consider, but I can't say I'd prefer either of those two. The email image implies more private communication and would fit better somewhere like You've got mail, and the person with the message bubble still has the issue of symbolizing only "talk", which is already a given at a talk page. &#123;{u&#124; Sdkb  }&#125;  talk 22:27, 28 July 2020 (UTC)
 * OK, sure. I guess my problem is that I'm having a really hard time seeing Symbol watching blue lashes.svg, due to low contrast, (sorry, bad eyesight) but I'm not against an eye, or even the current eye. How about ? Psiĥedelisto (talk • contribs) please always ping! 22:53, 28 July 2020 (UTC)
 * , the low contrast is definitely a concern we should address for accessibility; anyone want to edit File:Symbol watching blue lashes.svg? We could also make it larger, as in Symbol watching blue lashes.svg; would that look better? &#123;{u&#124; Sdkb  }&#125;  talk 22:57, 28 July 2020 (UTC)
 * I can see it a bit better, and do like the bigger version, even if I edit it. If I edit it, I'll make the inner eye take on the colors of Twemoji12_1f9ff.svg, except with a green iris for increased visibility. Are you all right with that? Psiĥedelisto (talk • contribs) please always ping! 23:05, 28 July 2020 (UTC)
 * , yep, that sounds good! &#123;{u&#124; Sdkb  }&#125;  talk 23:11, 28 July 2020 (UTC)
 * Voilà: Symbol watching blue lashes high contrast.svg Psiĥedelisto (talk • contribs) please always ping! 23:44, 28 July 2020 (UTC)

Follow-up
Does anyone else want to weigh in here? I think the image Psiĥedelisto has designed is an improvement on the status quo, so if there are no objections, I'll implement it in a few days. &#123;{u&#124; Sdkb  }&#125;  talk 23:03, 28 August 2020 (UTC)
 * ✅ &#123;{u&#124; Sdkb  }&#125;  talk 02:18, 14 September 2020 (UTC)

Creepy icon
The eye icon is very creepy and discomforting. Please use megaphone icon instead of the creepy eye icon. the purpose will be better served that way.--Walrus Ji (talk) 03:41, 18 December 2020 (UTC)
 * Hi ! This discussion is from a few months ago. If you'd like to change the icon again, I would suggest finding a specific megaphone icon to propose as an alternative and starting a new section below. &#123;{u&#124; Sdkb  }&#125;  talk 06:01, 18 December 2020 (UTC)
 * I kinda agree. I think it's the eyelashes that particularly make it disturbing. Nardog (talk) 15:11, 18 December 2020 (UTC)

Error handling
This template doesn't currently have any way of error handling (i.e. displaying an error message if you forget to include a page or some other mistake). I took a stab at adding that here, but the template's code is such a mess, it'd be good if someone else looked it over (and ideally simplified the template's code overall) before making a request to implement. &#123;{u&#124; Sdkb  }&#125;  talk 23:41, 22 July 2020 (UTC)
 * Well, have you given up on the above edit request? Because this broke it. You could have made a new sandbox, /sandbox2; popular templates like Citation do it all the time. Please move this to /sandbox2 and restore . Psiĥedelisto (talk • contribs) please always ping! 17:52, 25 July 2020 (UTC)
 * , I still support your edit request. They don't normally take this long to get answered, so I'm not sure what's causing the backlog. Regarding the sandbox, I did refactor above so that the link goes to the permanent revision for your request, so it should hopefully be fine, but let me know if there is some remaining issue. I'm not sure how much of a consensus there is behind the idea of having multiple sandboxes for a template, but it's something I think we generally ought to avoid. &#123;{u&#124; Sdkb  }&#125;  talk 04:38, 26 July 2020 (UTC)
 * Ah, yes, okay. Well, this issue is now moot, but FYI, I had gotten used to using the template as . So that was the reason I complained, sorry, did not really check if you broke my ER, just assumed as the sandbox stopped working. In re: multiplicity of sandboxes, doesn't seem a big deal to me. We do it in module space all the time, since you can't put modules in user space. Psiĥedelisto (talk • contribs) please always ping! 21:52, 28 July 2020 (UTC)

Buggy section parameter
Did the edits in affect the use of the section parameter? The documentation is... weird, but I can't seem to add  without adding ]]|undefined to the end of the location and the header (if not explicitly provided). ~ Amory <small style="color:#555"> (u • t • c) 12:59, 9 September 2020 (UTC)
 * Yeah, that looks to be an error. Looks like I fixed it in the sandbox, but mind double-checking before I push Special:Diff/969669761/977544361 live? Best, —&#8205;Mdaniels5757 (talk &bull; contribs) 13:43, 9 September 2020 (UTC)
 * , that seems to fix that issue.More broadly, is the idea to deprecate/remove the section parameter entirely? Something like   doesn't work as I'd expect, but from the documentation I can't tell if it was ever supposed to.  It's not clear that section does anything, unless piped is also given.  That seems wrong? ~ Amory <small style="color:#555"> (u • t • c) 18:14, 9 September 2020 (UTC)
 * , I've gone and put your fix in. What do you think about the section stuff, though? ~ Amory <small style="color:#555"> (u • t • c) 11:11, 14 September 2020 (UTC)
 * Sorry for missing your earlier ping. I have no clue what is up with the "section" parameter, to be honest--I don't have an opinion on it. —&#8205;Mdaniels5757 (talk &bull; contribs) 14:32, 14 September 2020 (UTC)

Move hidden comment before signature?
I think the hidden comment coming after the signature is what's causing this to make duplicate signatures with the new discussion tool. Would it be alright to move it before the signature? &#123;{u&#124; Sdkb  }&#125;  talk 23:54, 25 January 2022 (UTC)