MacFan4000
|
Phabricator Herald rule
editHi, could you please disable phab:H340? See Phabricator/Help/Herald Rules: Instead of rules like "Subscribe me to task if it is associated with project Foo", watch the project. Thanks! --AKlapper (WMF) (talk) 01:46, 29 January 2020 (UTC)
- @MacFan4000: No reply within three weeks, so I deleted phab:H340. For the records, the Herald rule was: "If Project tags include any of #Tool-Zppixbot, #User-MacFan4000, #Refreshed, then take these actions every time this rule matches: Add @MacFan4000 as subscriber." --AKlapper (WMF) (talk) 10:30, 18 February 2020 (UTC)
- A lot of people have rules like that, not just me. MacFan4000 (talk) 16:28, 29 May 2020 (UTC)
- @MacFan4000: Hi, could you please disable phab:H366 which looks like the very same situation? Please subscribe to projects instead of using Herald rules for this. Please see Phabricator/Help/Herald Rules. Thanks, --AKlapper (WMF) (talk) 17:11, 29 January 2021 (UTC)
- A lot of people also get asked not to do this when I get aware of this. So this is not about just you. :) --AKlapper (WMF) (talk) 17:12, 29 January 2021 (UTC)
- @MacFan4000: Hi, could you please disable phab:H366 which looks like the very same situation? Please subscribe to projects instead of using Herald rules for this. Please see Phabricator/Help/Herald Rules. Thanks, --AKlapper (WMF) (talk) 17:11, 29 January 2021 (UTC)
- A lot of people have rules like that, not just me. MacFan4000 (talk) 16:28, 29 May 2020 (UTC)
FR translation completed. Christian 🇫🇷 FR (talk) 08:31, 2 May 2021 (UTC)
Брауни для вас!
editTy for Skin:Library MrGorun (talk) 23:29, 11 August 2021 (UTC) |
Mediawiki Skins
editHi! I am trying to view Mediawiki Skins, and I see I need to contact you for that. Can you help out? Thank you! Misshiller (talk) 15:57, 15 November 2021 (UTC) skins.toolforge.org/wiki/Main_Page "Welcome This wiki showcases all of the currently maintained MediaWiki skins. Please contact MacFan4000 if you need an account here."
If you go to the skin page here on MediaWiki, there should be an example linking to the wiki so that it uses that skin. MacFan4000 (talk) 23:08, 16 November 2021 (UTC)
MediaWiki 1.38
editFR translation completed. Christian 🇫🇷 FR (talk) 17:06, 7 June 2022 (UTC)
A barnstar for you!
editThe Special Barnstar | |
For looking after https://skins.toolforge.org/ [[kgh]] (talk) 08:42, 22 August 2022 (UTC) |
Request for feedback on the Translation Notifications extension
editHello,
I’m Abijeet Patro. I’m a software developer in the Language team at the Foundation. I work on the Translation Notifications extension. I’m reaching out to you because you’ve previously used the extension, and we’re looking to gather feedback on how the extension can be made more reliable.
You can leave your feedback on a thread that we’ve started on the Babylon talk page.
Thanks for your time.
Regards,
Abijeet Patro (he/him)
Staff Software Engineer, Language Engineering
APatro (WMF) (talk) 12:36, 2 January 2024 (UTC)
Skins' compatibility with newer releases of MediaWiki
editI saw you made a bunch of edits which marked various skins as "unstable" on the grounds of them not being compatible with MW 1.42. As someone maintaining or at least participating in the maintaining of some of those skins (Skin:Liberty, Skin:Onyx; Skin:Anisa and Skin:Tempo regarding your edits in December '23), I'd like to know more details about the issues in question in order to be able to potentially implement support for 1.42(+) for said skins.
Now, I develop for the LTS release (1.39 currently) because a day only has so many hours and given MediaWiki's current pace, it's just not possible for a single person to keep up with a bunch of WMF teams. Though I have no hard data one way or the other, I suspect more and more production-grade sites out there are shifting to LTS releases, and for these sites' needs, the skins aren't unstable if and when they've been tested with and work just fine on 1.39, yeah?
You've been around for long enough that I don't need to tell you how to report a bug, but I am asking you to please report the incompatibility issues on Phabricator and tag them appropriately with the relevant skins' tags so that people (like me!) can become aware of the issues and work towards fixing them. :) Of course there are many issues which do require breaking backwards compatibility with older MW releases, but...let's cross that bridge when we do, yeah? Likewise, there are many issues a developer who's been around for a while can fix even if they don't have a devbox running these newer versions of MW. It's hard to say anything one way or the other without knowing the details, i.e. what happens when you install the skin on, say, 1.42.
In any case, please feel free to ping me, whether here or on Phabricator, about skinning-related issues, whether bugs or if you need code review, etc. I can't promise I'm able to fix everything, but I definitely do care! Jack Phoenix (Contact) 02:57, 29 June 2024 (UTC)
- Liberty and Onyx error with Error: Class "ResourceLoaderSkinModule" not found, this is due to the old aliases for classes being removed upstream. MacFan4000 (talk) 03:20, 29 June 2024 (UTC)
- Thank you for the reply.
- For Liberty, it looks like Jon fixed this back in February, so you just need to update your local working copy.
- For Onyx, this problem was indeed there and given that Halopedia is on 1.39.x already, I've taken the liberty to fix the issue and require MW 1.39+ for Onyx.
- Now, what about Anisa and Tempo? It looks like James F. did the ResourceLoader module class rename for both skins ~5 months ago, so that shouldn't be an issue for either of those. Jack Phoenix (Contact) 14:19, 29 June 2024 (UTC)
- Anisa and tempo were 1.41 era issues that have since been fixed. On a side note Onyx still errors, as seen at [1] seems like the futureproofing check is no longer working properly. MacFan4000 (talk) 14:56, 29 June 2024 (UTC)
- Thanks again for the report! The Onyx issue is hopefully fixed by this commit; I tested it on my 1.39 box and added some
error_log()
calls to ensure that the correct path is being hit. (And having typed that, I now realize I could've just dropped the legacy path altogether since Onyx now requires 1.39+...d'oh! Well, guess that's something to address in a future commit, then.) Jack Phoenix (Contact) 00:19, 30 June 2024 (UTC)- There is still yet another issue with Onyx, per the previous link. The Hooks class was dropped in 1.42 (methods have been deprecated since MW 1.35). MacFan4000 (talk) 01:37, 1 July 2024 (UTC)
- FWIW the same issue is present in Skin:Poncho. MacFan4000 (talk) 01:47, 1 July 2024 (UTC)
- There is still yet another issue with Onyx, per the previous link. The Hooks class was dropped in 1.42 (methods have been deprecated since MW 1.35). MacFan4000 (talk) 01:37, 1 July 2024 (UTC)
- Thanks again for the report! The Onyx issue is hopefully fixed by this commit; I tested it on my 1.39 box and added some
- Anisa and tempo were 1.41 era issues that have since been fixed. On a side note Onyx still errors, as seen at [1] seems like the futureproofing check is no longer working properly. MacFan4000 (talk) 14:56, 29 June 2024 (UTC)