- User Since
- Feb 22 2019, 5:51 AM (213 w, 4 d)
- LDAP User
- MediaWiki User
- Setian~mw [ Global Accounts ]
Mar 3 2019
Mar 1 2019
Here's a mockup I created. https://upload.wikimedia.org/wikipedia/mediawiki/2/27/Screenshot-localhost-2019.02.28-22-39-30.png
Feb 28 2019
So where should the log entries get saved? Is this going to the move/revision log, kinda like how currently, revisiondelete actions go to the delete/revision log?
So what's the user interface for this going to look like? I'm thinking it's going to be like a cross between action=revisiondelete and Special:MovePage, because it'll list the revisions being moved and then ask where they're being moved to.
I created this mockup: https://upload.wikimedia.org/wikipedia/mediawiki/d/d2/Screenshot-localhost-2019-02-26-23-07-41.png
Feb 27 2019
The situation is complicated by the fact that there are two tables for storing revisions, the archive table and the revision table.
T215696 ("RecentChanges should update entries when user move a page") may help with this.
@Anthony_Appleyard So if logged actions are being taken to move archived revisions from one page title to another, what log would these entries be filed under? Move log? Deletion log?
@Anthony_Appleyard So basically you want something along the lines of this, it sounds like. https://upload.wikimedia.org/wikipedia/mediawiki/d/d2/Screenshot-localhost-2019-02-26-23-07-41.png
Feb 26 2019
So what's going to happen to these null revisions? Will they just get deleted? What happens if the move is reversed; should those deleted null revisions get automatically restored, or should a sysop have to come along and restore them?
This goes well with T217089, "Add a config setting to disable deletion of recentchanges entries when pages are deleted."
This task dovetails nicely with T217125, "Set $wgGroupPermissions['*']['deletedhistory'] = true; in DefaultSettings.php".
How do we want to implement this? As a core user right, or as a hook that an extension would use to add a new user right?
Maybe T215696 ("RecentChanges should update entries when user move a page") would help with this?
Feb 25 2019
This looks to be automagically taken care of (going forward) when this patch is applied. The "originally created as" simply doesn't appear for newer entries.
So how do you want to do this; should it be set up like:
Feb 24 2019
There's going to be a need for cross-wiki invalidation of caches, right, when pages are deleted, etc.? How are we going to implement that?
@Legoktm , I took a look at your 2014 patch here: https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/177960/5/includes/cache/LinkCache.php
Feb 23 2019
Here are the current error messages I get (when using mysql Ver 15.1 Distrib 10.1.34-MariaDB, for debian-linux-gnu (x86_64)):
Are there certain mw.log entries, like previous page moves, whose recentchanges rows should be left alone rather than changed when the page is moved? If so, what's the list of exclusions? Anyway, for now I just went ahead and excluded all mw.log entries from being changed by this.
Adding Legoktm since he wrote the LinkRenderer.
Do you want to have an isset() for $wgInterwikiNamespaces, or do you want it defined in DefaultSettings.php as an empty array, or is there some better way to find out the namespace scheme of another wiki?
What documentation should a newbie read to learn how to do this? Oh, I guess I'll take a look at https://phabricator.wikimedia.org/project/profile/1087/ for inspiration.
Feb 22 2019
So now I'm starting to think, since this is going to have so many of the features and aesthetics of AbuseFilter, the best approach would be to just rip off most of the code from AbuseFilter, and rip off a small amount of code from SpamBlacklist (the part that compares the blacklist to the whitelist to see if it's going to be triggered). In a case like this where the needed functionality is so close to what already exists, might as well just rip it off wholesale, rather than merely take inspiration from it.
It looks like most of the consensus is in favor of creating a special page of some sort for the spam blacklist, since this task hasn't been WONTFIXed.
So, a few questions.
- Are we anticipating there are just going to be 3-4 options?
- Are we going to want to integrate this with AbuseFilter; and if so, how does that affect our design decisions?
- Do you mind if we have to create another database table for this?
- If we do this as a special page, how do we handle situations where sysops want to insert a line next to an already-existing line, so that similar items are grouped together? Is each line going to be numbered, so that for example, they could number a new line 65 to put it between lines 60 and 70?
Just curious, is the RTL version actually used anywhere? I ran a Catfish search and didn't see it in any of the files, although the LTR version is used in VisualEditor/modules/ve-mw/ui/styles/tools/ve.ui.MWLinkInspectorTool.css
What table will it be looking at for this timestamp? Also, what style of notice will it be displaying; is there another one like it, that it can be modeled after? Thanks.