Sat, Dec 8
Thu, Dec 6
This was already done in Theme v. 2.1. (commit 5ef8e8f801ae74e537237b853737f0ad2f4b12c2 / Change-Id I55397f13efcd3407e91772903fefa041b1c18e57), merged on 9 July 2017.
Tue, Nov 27
EditAccount doesn't currently support AuthManager (T135264) and is bascially abandonware at this point. Given that and the fact that EditUser exists, I think it'd make more sense to update EditUser to support whatever EditAccount currently has that EditUser doesn't (I guess the "this account has been disabled" banner is one such feature?) and archive EditAccount altogether.
Thu, Nov 22
Sep 11 2018
Maybe the OpenGraphMeta extension could be of use here?
Aug 27 2018
Aug 26 2018
Aug 23 2018
Aug 10 2018
Instead of such a "nuclear option" which re-introduces T200148, you should set a more appropriate top value for #coordinates. Based on some quick testing 0.1em seemed to work well enough to restore/keep the current behavior while still allowing to remove that position: static; from #mw_content. Additionally it should play nicer with the site notice when one is present.
Aug 3 2018
How come CI tests cannot be run for Oracle and MSSQL (T197995) due to the Docker images not being freely licensed, but for a trivial task for which there are (probably better) FOSS replacements proprietary software is suddenly okay and acceptable? This makes no sense whatsoever.
Aug 2 2018
In MediaWiki i18n sentence case is preferred and the same appears to be true for many, if not all, WMF projects (e.g. this English Wikipedia page, currently referenced on the main page, is titled "July 2018 lunar eclipse", not "July 2018 Lunar Eclipse") so not following estabilished conventions makes about as much sense as capitalizing "Wikimedia" as "WiKiMeDiA" or somesuch -- in other words, it doesn't make sense and seems just out-of-place and wrong.
Aug 1 2018
Jul 27 2018
Jul 25 2018
Seems to be working correctly now, but I remember this happening at some point during the last week or the past couple weeks. Turns out it was due to extreg-wos hitting...Phabricator's rate limits, unsurprisingly. Not sure what's the current status of those rate limits and exemptions, but I don't think Labs is going to get whitelisted the same way WMF/WMDE offices were (T198612).
Sounds like you've got a nice v4 roadmap here. :)
Ditto for me on Fennec 60.0 (still on the same device) on Brickipedia. Maybe this is akin to T181491 -- a browser-specific bug manifesting itself only in older (=not the latest) versions of Firefox.
Jul 22 2018
All of the uploading special pages are more or less copypasta of each other (see also T198154...); the concept of "default avatars" was always a thing, the concept of "default gifts/awards" was never a thing, though maybe it should be. Patches welcome, as always. :)
Jul 21 2018
Jul 18 2018
Jul 15 2018
The NoTitle extension introduces the __NOTITLE__ magic would for that.
Please let's not. Adding a new skin which is essentially a fork of Vector with merely a different color scheme would be an unnecessary maintenance burden on pretty much everyone involved. A far more superior and maintainable approach would be the Theme extension I mentioned, once the extension would be reviewed by the security team as well as otherwise scrutinized to be suitable for WMF deployment. That extension provides the capability to rather easily "extend" skins with alternate color schemes, and it goes without saying that reviewing ~200 lines of CSS(/LESS) is a lot easier than 1k+ lines of PHP, CSS/LESS and JS.
Jul 14 2018
This is already doable via the Theme extension, which is installed on ShoutWiki sites as well as various other wikis. By default the Theme extension provides 2 Vector themes and 3 MonoBook themes (see https://www.mediawiki.org/wiki/Extension:Theme#Available_themes). Custom skins (like Bouquet or Gamepress) can register their own themes in the skin's setup file.
Jul 13 2018
What is a "widely used extension", exactly? Before we can determine what, if anything, to do, we need to determine what projects are affected.
Jul 11 2018
UserStats has had its own extension.json file (see T152865) since December 2017 (see Change-Id: Ib934825e7c086ae8b30f975a34edeb02355e1ba8) where $wgUserStatsPointValues is given a default value, so I guess this is fixed.
Jul 9 2018
I think it'd make sense to have this group. Ideally the group would have +2 rights to all Social-Tools extensions. Currently each extension has two groups which have +2 rights to it (in addition to core +2'ers, of course): ShoutWiki and the respective extension-<extension name> group (e.g. extension-Comments for Comments, etc.).
This stuff was added last October. Granted, the documentation is pretty generic, but I'm sure it can be improved in collaboration with translators, should PictureGame ever be made translatable via TWN.
Seems like that -- it certainly was reproducible and fixable when I wrote the patch, but now I also can't reproduce it with Firefox 61.0 on Ubuntu 18.04.
Jul 8 2018
Jul 7 2018
Jul 4 2018
After looking a bit into this:
- Turns out the DB query in getFromDatabase() is commented out because it refrences columns which don't exist in the user_board table. That table does not have a column called ug_user_id_to but it does have ub_user_id; furthermore there isn't a ug_status or any equivalent to that.
- Therefore it is not possible to retrieve the amount of new board messages a user has by querying the DB because this is never stored in the DB, only in memcache.
Jul 1 2018
Jun 29 2018
Jun 28 2018
Jun 27 2018
I wrote a patch which should hopefully fix the issue you encountered. Once someone reviews it and merges it into master, you should redownload the Html2Wiki extension (for example, via MediaWiki.org's ExtensionDistributor page) -- remember to choose "master (latest development version)" version instead of "1.31 (latest stable version)" from the drop-down menu and replace your old copy of the extension with the new copy. After that the issue should be gone, I hope!
@Gryllida Is this still happening? I was unable to reproduce this bug on MediaWiki.org.
Jun 26 2018
Jun 25 2018
Sorry, I don't have one available right now. :-( I'll try to get someone to help me fix the canonical test wiki -- it was running MW 1.30 and I tried upgrading it to 1.31 without knowing that the server doesn't have either of the necessary requirements, and as you know, I'm not much of a server admin. (This bug should be *relatively* easily reproducible by installing SocialProfile + the Nimbus skin and maybe setting up a few user levels and then making an edit or two (in a namespace where the edits count towards point totals -- NS_MAIN by default). A bit more complicated than just slapping a wfLoadExtension call into LocalSettings.php, but not a total nightmare. ;-)
Jun 24 2018
Well I ended up fixing this sooner than I thought I would.
Surprising to see that the patch didn't fix it, but that indeed appears to be the case. Here's a slightly different comparison for us who are not so well versed in Chinese, using the Serbian (sr) Wikipedia as an example: sr.wikipedia main page with variant=sr-ec (Cyrillic) vs. sr.wikipedia main page with variant=sr-el (Latin).
In both cases, #p-banner's text is Википедија, though it should be this only for the Cyrillic variant and for the Latin variant it should be Vikipedija.
This appears to be easily reproducable and not dependent on the user's login state.
Hi @GentillePlume, is this issue still happening? I was unable to reproduce this on the 1.31 release version of Timeless.