User talk:CalendulaAsteraceae
| ||
Issue with Module:Bicolor, Template:Bicolor9, and similar templates
[edit]I've noticed an issue with {{Bicolor9}}, {{Bcolor Y}}, {{Bicolor X}}, {{Bicolor2}}, and {{Bicolor3}}.
On those templates' pages, the documentation subpage won't appear properly. The post-expand include size is also large enough that each of those templates is listed in Category:Pages where template include size is exceeded:
- {{Bicolor2}}: 2,057,889/2,097,152 bytes
- {{Bicolor3}}: 2,037,777/2,097,152 bytes
- {{Bicolor9}}: 1,711,055/2,097,152 bytes
- {{Bicolor X}}: 1,688,286/2,097,152 bytes
- {{Bcolor Y}}: 1,837,733/2,097,152 bytes
My guess is that this results from a case of too many non-rendered tranclusions. Curiously, none of the issues happen with {{Bicolor4}} (which doesn't have a documentation subpage), even though it also uses the new parameters you added to Module:Bicolor for {{Bicolor}} to use. Might it be from not using {{TemplateBox}} in each documentation subpage? Shāntián Tàiláng (talk) 20:14, 28 February 2024 (UTC)
- Oof, yeah. IIRC this is because the template is including all the color combinations and then hiding the ones that don't have corresponding categories, which is, it turns out, a lot of combinations. This is arguably an improvement on the previous code where it was calling ifexist on every category (and putting pages in Category:Pages with script errors thereby) but, you know, only arguably. Ideally I'd like to add some sort of filter to Module:Bicolor for which categories exist which is less expensive than ifexist (get a list of all a category's subcategories?), but I'm not really sure how one would do that. —CalendulaAsteraceae (talk • contribs) 03:31, 29 February 2024 (UTC)
- @CalendulaAsteraceae: Let me see if I understand the issue. These set of templates (via {{Bicolor}} and
{{#invoke:Bicolor|bicolor}}
) are generating a large number of links (to pages in Category namespace) based upon permutations of two colors from a list of about 50 colors. I am not sure I fully understand how the these are "hiding the ones that don't have corresponding categories". Is this via this bit of CSS magic: Template:Bicolor/styles.css#L-20 (i.e., the "redlinks" display is being altered)? It seems the template (prior to its conversion to Scribunto Lua) used to employ the{{#ifexist:}}
parser function to filter these permutation vs. just hiding the display of the links on the page as it does now and you want to return to filtering the list instead of hiding entries is this correct? —Uzume (talk) 23:52, 10 March 2024 (UTC) - As for possible solutions, we need to further understand that this is a large page caching issue as the resulting page output is dependent upon all the pages it links to (or else the page cache will not know when to update the cache entry when one of its link targets changes, e.g., its existence, etc.).
{{#ifexist:}}
is explicitly "expensive" (and creates a transclusion dependency link) exactly for this reason (although a large number of regular links can also cause a similar issue due to "redlinks" display, etc.). There are Scribunto Lua equivalents to{{#ifexist:}}
(i.e,mw.title.new().exists
), however, most of them are also "expensive". That said, I believe one can manually create transclusion links viamw.title:getContent()
without incurring an "expensive" hit.getContent()
should take care of the page caching dependencies and the code can decide base upon thenil
returned when the page does not exist. —Uzume (talk) 23:52, 10 March 2024 (UTC) - @Shāntián Tàiláng: I tested this in the sandbox and have deployed it via 859483298 since they were already seemingly broken and my sandbox tests seemed to do no worse. Now we just need to do something similar for {{Tricolor}}. —Uzume (talk) 23:52, 10 March 2024 (UTC)
- I just realized this might get noticed though as it create piles of transclusions to categories, including many missing ones. I guess we shall see who shows up to complain. Here are the new numbers: —Uzume (talk) 23:56, 10 March 2024 (UTC)
- {{Bicolor2}}: 73,580/2,097,152 bytes
- {{Bicolor3}}: 109,812/2,097,152 bytes
- {{Bicolor9}}: 46,413/2,097,152 bytes
- {{Bicolor X}}: 72,645/2,097,152 bytes
- {{Bcolor Y}}: 44,728/2,097,152 bytes
- {{Bicolor4}}: 145,386/2,097,152 bytes
- Thank you for taking care of this! —CalendulaAsteraceae (talk • contribs) 03:26, 16 March 2024 (UTC)
- I just realized this might get noticed though as it create piles of transclusions to categories, including many missing ones. I guess we shall see who shows up to complain. Here are the new numbers:
- @CalendulaAsteraceae: Let me see if I understand the issue. These set of templates (via {{Bicolor}} and
Hi CalendulaAsteraceae!
Are you still planning to use this module? I'm cleaning up references to internal mbox classes at the moment, in preparation of moving some of its styles from MediaWiki:Common.css to Template:Mbox. I noticed Module:Fmbox was created last year by you and makes use of some of these classes. I imagine it's easy to make that a wrapper around Mbox and/or to load the same styles, but for now I've skipped it until I know that it's actually needed. Let me know if you want any help! More details at Template talk:Mbox#TemplateStyles. Krinkle (talk) 00:31, 17 March 2024 (UTC)
- @Krinkle: Thanks for checking! I have no memory of creating that module, so don't worry about it! —CalendulaAsteraceae (talk • contribs) 01:17, 17 March 2024 (UTC)
Copyright status: File:The Dancing Master, Playford, 1686.djvu
[edit]Copyright status: File:The Dancing Master, Playford, 1686.djvu
This media may be deleted. |
Thanks for uploading File:The Dancing Master, Playford, 1686.djvu. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.
If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.) If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there. Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you. |
This action was performed automatically by AntiCompositeBot (talk) (FAQ) 06:05, 3 May 2024 (UTC)
Hello again! Sorry to bother, but is it possible to update this svg to the 2015 map? The differences aren't major, but for the English Wikipedia's FAC process, the 2015 map uses the World Health Organization as its source and will be seen as more reliable. This is the correct png version. I can't do it myself because I get the "unsafe CSS" error again even when trying to upload a new version. I'm really, really sorry for the trouble.
Also, separately and purely for my own curiosity, how did you download that 2016 map in the first place? That existed on Commons beforehand, but I couldn't get OWID to reproduce it and I assumed they'd long since deleted it for some reason. If there's a URL to link to, I'd like to update that Commons file. Ed [talk] [OMT] 03:45, 18 August 2024 (UTC)
- Any chance of getting help with this? Sorry again. Ed [talk] [OMT] 23:00, 6 September 2024 (UTC)
Hello, since fmbox and fmbox-system will be deprecated as classes in Common.css soon, I advise you change this module to use Module:Message box for messages. —Matrix(!) ping onewhen replying {user - talk? - uselesscontributions} 17:16, 2 November 2024 (UTC)
- Thanks for the heads-up! Done. —CalendulaAsteraceae (talk • contribs) 10:09, 3 November 2024 (UTC)