User Details
- User Since
- Aug 22 2016, 6:14 PM (171 w, 6 d)
- Availability
- Available
- LDAP User
- Pppery
- MediaWiki User
- Pppery [ Global Accounts ]
Fri, Dec 6
Thu, Dec 5
Do the two merged patches have to be from this year, or do merged patches from past years of google code in count?
The actual behavior I noticed and wrote a patch to fix was that the error message shows up twice if you use the same translation unit name three times in one page. It is possible that there is some other cause for this duplicate error message that I was unable to reproduce and this patch may not fix.
This feels like it was almost too easy for a GCI task, given how little time it took me to code.
Wed, Nov 27
Sat, Nov 23
Nov 5 2019
(I've retokened and deprojected the task based on the assumption from your comment that this task is now being treated as the "add a new user right to allow this" case; I still feel that doing this without a user right needs consensus)
Nov 4 2019
Nov 3 2019
Oct 24 2019
The Gadget namespace already has pages in it. The argument that "the namespace has to be empty for technical reasons" has been unanimously rejected at RfD in 2017
Oct 23 2019
Oct 21 2019
I believe bug was introduced by the fix to T234368.
If the request is reframed to add a user right to allow the deletion of pages that have always been redirects during page moves, regardless of target, then no I do not feel that needs consensus. I would even support the granting of that right to page movers. You would, however, need to retitle and redescribe the task accordingly.
Oct 19 2019
Oct 6 2019
The ability to move a page over a redirect that has multiple redirect revisions, all of which point to the same page, is a useful feature, which I don't expect to be controversial.
Oct 4 2019
Oct 3 2019
Oct 1 2019
Sep 30 2019
Sep 22 2019
Sep 19 2019
Sep 12 2019
Sep 8 2019
Sep 6 2019
Aug 31 2019
Aug 26 2019
Aug 25 2019
Aug 21 2019
Aug 19 2019
Aug 6 2019
Aug 4 2019
Aug 2 2019
Jul 30 2019
Jul 22 2019
Jun 26 2019
This is not a bug. The pages really are transcluding themselves, as a consequence of a recent change to the CS1 module system.
Jun 4 2019
May 24 2019
May 23 2019
<removing link to topic on enwiki; the flow extension has since been uninstalled>
May 22 2019
May 19 2019
May 18 2019
May 11 2019
May 3 2019
Apr 29 2019
Apr 27 2019
Apr 25 2019
I don't think that such an extreme measure is a good idea; many users (including me) use CSS displaytitles on their userpages. Perhaps a better idea would be to ignore specific CSS properties.
Apr 16 2019
Apr 14 2019
Special:UserLogout isn't blacklisted; the entire special namespace is
Apr 9 2019
Apr 2 2019
See also T217217, an identical bug for visual and 2017 wikitext editors
Mar 26 2019
Mar 12 2019
The example I provided doesn't work anymore, because the page was protected, but the bug still exists
Mar 1 2019
Feb 27 2019
Feb 24 2019
Strangely, this doesn't trigger when moving a page to a title that is just protected against creation.