User talk:Mike Peel
|
Quality Image Promotion[edit]
Your image has been reviewed and promoted
Congratulations! View from the Torre degli Asinelli, Bologna 2.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. ![]() |
--QICbot (talk) 05:23, 30 June 2022 (UTC)
Issues with Migrating to Art photo[edit]
In this edit you replaced "{{Information field|" with "{{Art photo|Wikidata=Q110713956 field|". Jarekt (talk) 12:14, 30 June 2022 (UTC)
- @Jarekt: Yes, the code would do that. I hadn't heard of {{Information field}} before, otherwise I'd have coded an exception for it - too late now. Hopefully there shouldn't be too many cases with that, though? (and maybe that's something that could be migrated into the information templates directly?). Thanks. Mike Peel (talk) 13:34, 30 June 2022 (UTC)
- I only found handful of files with this issue, so hopefully it is not a widespread problem. {{Information field}} is a bizarre legacy template which when added to "other_field" of {{Information}} and other templates can add additional fields, with any text, to the infobox, by benign en:Code injection. It can be useful, especially when creating custom infobox templates, but can easily lead to pages with invalid html. It is already integrated with all infobox templates so there is nothing to migrate. --Jarekt (talk) 13:50, 30 June 2022 (UTC)
- @Jarekt: OK. I was thinking more like having "name1", "field1" lines and directly supporting the additions in the information templates, rather than the code injection approach. But better would be to just migrate them into normal fields / structured data anyway. I know nothing more about how it's used beyond this discussion, though, so perhaps it's just a rabbit hole to avoid. Thanks. Mike Peel (talk) 15:13, 30 June 2022 (UTC)
- I only found handful of files with this issue, so hopefully it is not a widespread problem. {{Information field}} is a bizarre legacy template which when added to "other_field" of {{Information}} and other templates can add additional fields, with any text, to the infobox, by benign en:Code injection. It can be useful, especially when creating custom infobox templates, but can easily lead to pages with invalid html. It is already integrated with all infobox templates so there is nothing to migrate. --Jarekt (talk) 13:50, 30 June 2022 (UTC)
Quality Image Promotion[edit]
Your image has been reviewed and promoted
Congratulations! Beeston Castle 2016 001.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. |
Your image has been reviewed and promoted
Congratulations! Benin Bronzes, Horniman Museum 2.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. |
Your image has been reviewed and promoted
Congratulations! Møller Centre, Churchill College, Cambridge.jpg, which was produced by you, was reviewed and has now been promoted to Quality Image status. If you would like to nominate another image, please do so at Quality images candidates. We also invite you to take part in the categorization of recently promoted quality images. |