This template is within the scope of WikiProject Photography, a collaborative effort to improve the coverage of
photography on Wikipedia. If you would like to participate, please visit the project page, where you can join
the discussion and see a list of open tasks.PhotographyWikipedia:WikiProject PhotographyTemplate:WikiProject PhotographyPhotography articles
This template is within the scope of WikiProject Graphic design, a collaborative effort to improve the coverage of
graphic design-related subjects on Wikipedia. If you would like to participate, please visit the project page, where you can join
the discussion and see a list of open tasks.Graphic designWikipedia:WikiProject Graphic designTemplate:WikiProject Graphic designGraphic design articles
Image
Shouldn't the image on the tag actually be a featured picture? The Mona Lisa image is too small to be featured as of now.
BrokenSegue 03:05, 26 Jan 2005 (UTC)
I added the Mona Lisa image because that painting is widely regarded as a masterpiece—people automatically think of fine artwork when they see it, and so it's a natural choice for Wikipedia's finest images. By contrast, I don't think any of our featured pictures have quite that level of universal recognition and admiration. --
bdesham 04:39, 26 Jan 2005 (UTC)
Conflicts with metadata box
You will notice on images like
Image:Praying_mantis_india_2.jpg that the featured picture template overlaps with the box. The problem also occurs with
Template:Wallpaper,
Template:cc-by-sa-2.5 and probably others... However,
Template:GFDL seems to scale properly to fit with the box instead of conflicting with it. I tried to fix it, however, I failed. So, if anyone could make it it work properly that would be great. The best example is
here, which is
Image:Wfm stata center.jpg before I added
Template:Clear to avoid the problem... only the GFDL notice doesn't conflict... any help in resolving this for (all) template would be great.
grenグレン09:11, 13 September 2005 (UTC)reply
I second this. Every time I see one of these things, I'd like to be able to see what people said and how consensus emerged. This is very helpful with featured articles, since someone contemplating an FA nomination of their own can get an idea what the standards are. Shouldn't be any different with FPs.
Daniel Case05:21, 5 March 2006 (UTC)reply
Former featured picture
Should we have a "former" template for pictures, too, as a courtesy to the creators? I ask because there is currently an active period of de-listing FPs. --
Janke |
Talk07:04, 19 April 2006 (UTC)reply
This sounds like a pretty good idea to me. What about this:
I've always thought this would be useful. I just tried to add some code to the template to allow a link to an image's nomination, using an optional parameter which if omitted will mean the template displays as it does now, so that all the current tags won't suddenly break. However, although I managed to get a similar sort of thing to work on {{featured}}, for some reason it won't work for me here. Maybe someone familiar with
m:ParserFunctions could have a look?
Worldtraveller16:12, 10 May 2006 (UTC)reply
Think I've fixed it, let me know if it still doesn't work. I'm going to try nesting the #if condition inside of #ifexist to check whether the FPC subpage already exists where it should, at /{{{PAGENAME}}}. Wish me luck! --
Visviva12:28, 26 May 2006 (UTC)reply
Someday someone will have to explain to me why FPC subpages are given random made-up titles, rather than following the actual image name. Bargle. I guess the #ifexist stuff could be taken out, unless there actually are some FPC subpages with sensible titles.
I don't think the test for a candidate page that has the same name as {{{PAGENAME}}} works right. I'm not sure MediaWiki can even do that. howcheng {
chat}23:11, 29 August 2006 (UTC)reply
Perhaps a short documentation page would be useful here; there is no mention, for one thing, of the feature by which one may enter a different name for the nomination's sub-page.
Waltham,
The Duke of15:19, 15 August 2010 (UTC)reply
Edit request from Kmartis, 13 September 2010
{{
edit protected}}
change newspaper title to Boston Gazette
Can you add the following code to this template?
{{#ifeq:{{#titleparts:{{PAGENAME}}|1|2}}|delist|[[Category:Featured pictured promoted through delist-and-replace]]}}
This will help organize issues related to delist-and-replace.
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Please undo this edit that was made without consensus that I object to. There is no reason that identified shouldn't be emphasized whether it is linked to a page or not.
— {{U|
Technical 13}} (
e •
t •
c)13:16, 9 July 2014 (UTC)reply
Reverted. (But it my opinion this was a beneficial change, as it looks ridiculous emphasising that word for no particular reason. So I expect that further discussion will support it.) — Martin (
MSGJ ·
talk)
16:18, 9 July 2014 (UTC)reply
@
Technical 13: I would say the key words/phrases in that sentence are "featured picture", then "finest images", then "members of the community", then "accompanying article". In my opinion, "identified" comes in at number five, if that. Why do you think it is such an important word - so important that it deserves more emphasis than "featured picture"? — Mr. Stradivarius♪ talk ♪21:50, 9 July 2014 (UTC)reply
Mr. S., it is the result of the implicit number one parameter. This gives it some weight, "featured picture" is already stood out from the rest of the text since it is a link, same with "members of the community". I have no issue with adding bold italics to "finest images", even though the phrase isn't apparently important enough to try and keep it on one line, and "accompanying article" should be linked. — {{U|
Technical 13}} (
e •
t •
c)22:04, 9 July 2014 (UTC)reply
@
Technical 13: I don't agree that the template code should have any weight on how the sentence should be bolded; the sentence should be bolded based on the structure of the sentence itself. If you ignore the template code, there isn't anything special about the word "identified" except when it is linked. That's why I changed it to not look special when it isn't linked, but to keep it in bold italics when it links to the nomination page. — Mr. Stradivarius♪ talk ♪23:17, 9 July 2014 (UTC)reply
No logical reason has been given as to why this formatting absurdity should remain, and no further comments have been expressed. So I will re implement shortly. — Martin (
MSGJ ·
talk)
10:50, 11 July 2014 (UTC)reply
Template-protected edit request on 13 August 2014
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Please replace
{{#switch: {{{category|¬}}}
| | no = <!-- Blank or "no", don't categorise -->
| #default =
{{{category|[[Category:Featured pictures|{{PAGENAME}}]]}}}<!--
-->{{#ifeq: {{#titleparts:{{{1|foo}}}|1|1}} | Delist
| [[Category:Featured pictures promoted through delist]]
}}
}}
-->{{#ifeq: {{#titleparts:{{{1|foo}}}|1|1}}|Delist|[[Category:Featured pictures promoted through delist]]}}
Currently
Category:Featured pictures is used to display the actual number of FPs on
WP:Featured pictures, and it wouldn't be good, if some of them could be left out of this category (which would make the above number incorrect).
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
I'd suggest we add the following:
{{Top icon
| imagename = cscr-featured.svg
| wikilink = Wikipedia:Featured pictures
| description = This is a featured picture. Click here for more information.
| id = featured-star
}}
Every other piece of featured content, to my knowledge, has a top star as well as any other indicator. This will make things consistent. Adam Cuerden(
talk)18:58, 22 July 2015 (UTC)reply
-->{{#ifeq: {{#titleparts:{{{1|foo}}}|1|1}}|Delist|[[Category:Featured pictures promoted through delist]]}}|}}<noinclude>
{{documentation}}
<!-- Categories go on the /doc subpage, and interwikis go on Wikidata. -->
</noinclude>
with
-->{{#ifeq: {{#titleparts:{{{1|foo}}}|1|1}}|Delist|[[Category:Featured pictures promoted through delist]]}}|}}<!--
-->{{if in page|%{%{%s*[Pp]icture ?of ?the ?day%s*{{!}}||[[Category:Featured pictures that have not appeared on the main page]]}}<noinclude>
{{documentation}}
<!-- Categories go on the /doc subpage, and interwikis go on Wikidata. -->
</noinclude>
@
Coffeeandcrumbs: I have no specific objections to this if you would find it useful, although it should be noted that you would still need more information than just this category in order to schedule POTDs, as they don't include information on when the image was featured, which you would need in implementing the FIFO criterion. Currently I use a desktop tool I wrote myself for probing for unused pictures, and sorting them into the correct order... I vaguely intended to make this publicly available at some point, through the cloud or toolserver or something, but I haven't got around to it yet and since I do most of the scheduling myself there hasn't been a pressing need yet. Cheers —
Amakuru (
talk)
15:31, 1 July 2019 (UTC)reply
@
Amakuru: So I kept asking for help and
Danski454 was kind enough to modify the syntax for me again. The version below not only adds the FPs to the "
not on MP yet" category but also sorts the category by the date the FP was promoted at FPC. I think it now accomplishes what your off-wiki app does and allows us to keep with FIFO. ---
Coffeeand
crumbs23:04, 1 July 2019 (UTC)reply
I just want to note that if the code cannot find the date of the nomination it will use the current date. This only affects pre-2007 promotions and malformed nominations, so should not be an issue considering the current POTDs are from around 2015.
Danski454 (
talk)
23:06, 1 July 2019 (UTC)reply
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Please replace
-->{{#ifeq: {{#titleparts:{{{1|foo}}}|1|1}}|Delist|[[Category:Featured pictures promoted through delist]]}}|}}<noinclude>
{{documentation}}
<!-- Categories go on the /doc subpage, and interwikis go on Wikidata. -->
</noinclude>
with
-->{{#ifeq: {{#titleparts:{{{1|foo}}}|1|1}}|Delist|[[Category:Featured pictures promoted through delist]]}}|}}<!--
-->{{if in page|%{%{%s*[Pp]icture ?of ?the ?day%s*{{!}}||[[Category:Featured pictures that have not appeared on the main page|{{#time:Y-m|{{if in page|%[%[Category:Featured picture nominations/(%P+)|%1||page=Wikipedia:Featured picture candidates/{{{1|{{FULLPAGENAME}}}}}|sub=yes}}}}]]}}<noinclude>
{{documentation}}
<!-- Categories go on the /doc subpage, and interwikis go on Wikidata. -->
</noinclude>
Done On the assumption that both the initial edit and this request were done in good faith, I have reverted without really looking at the code or trying to fix it. Let me know if you need help with testing. For reference, one of the pages in the error category was
File:Bell Miner 1 - Nepean Weir.jpg, if it helps with testing in the sandbox. There is a warning displayed when you edit
Template:Featured picture/sandbox. –
Jonesey95 (
talk)
06:46, 6 June 2022 (UTC)reply
Strange, when I did previews with the sandbox version it didn't show loop errors, but I must've missed something. Sorry about that. --
Ahecht (
TALK PAGE)
13:43, 6 June 2022 (UTC)reply
Template-protected edit request on 6 June 2022 - Bring back version
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
The previous edit request from before can now be brought back, as the core issue behind one of the templates used in it that caused a template loop has now been fixed. The sandbox is the latest version before the revision and can be used to transfer it over.
Aidan9382(
talk)10:31, 6 June 2022 (UTC)reply
Not done@
Aidan9382: sorry, but I have no idea what immediate edit you have tested and is ready to go live. Please point to a specific permalink on the sandbox that is ready to go live - give a summary here in the request of why the edit is being made - just as if you could edit the template directly and leave an edit summary. —
xaosfluxTalk13:35, 6 June 2022 (UTC)reply
@
Xaosflux: Sorry, let me explain. A recent edit was made to this template by a template editor. Said edit caused the template to start spamming Inifinite Template Loop errors. The previous request right above this one is me asking for it to be reverted. After it was reverted, the part that was causing the said issue (One of the templates used within it) has been fixed. Im essentially saying to revert the revert now that the error with it has been fixed. Does that make a bit more sense?
Aidan9382(
talk)13:41, 6 June 2022 (UTC)reply
@
Aidan9382 go to
Template history - which timestamp do you want restored to the current version? Is it 2022-06-06T01:30:33? Is the reason that something somewhere else is keeping these "loops" from occurring? Ping to
Jonesey95 who may want to deal with this. —
xaosfluxTalk13:46, 6 June 2022 (UTC)reply
@
Xaosflux: Yes, I'd like 01:30, 6 June 2022. The reason was down to one of the templates that was used within it ({{If in category}}), which has since been improved and the error has been sorted. Sorry for not clarifying that initially.
Aidan9382(
talk)13:49, 6 June 2022 (UTC)reply
On hold going to let this sit for a day to see if Jonesey95 has any feedback - someone else may process it in the meantime, if not I'll get back to it I'm sure (I try to patrol all the technical-type edit requests a couple of times a day) —
xaosfluxTalk13:51, 6 June 2022 (UTC)reply
Done I have restored
Ahecht's edit. The file I linked to above, and the sandbox (which has not been modified since the changes above) appear to be working fine without template loops. So far, so good, I think. –
Jonesey95 (
talk)
15:59, 6 June 2022 (UTC)reply