Allow searching also by new/target name on moving log page
Open, LowPublic3 Estimated Story PointsFeature
Actions

Assigned To

None

Authored By

	Cwek
	Apr 21 2014, 2:55 PM

Description

Now our moving log only searchs the moving action by the source page's name, but we can't searchs the action by the target page's name.

Though we can check out the moving action in the page history or find the redirection which was the source page's name by some tools,we can't find the redirection which is deleted,or it's too hard to find it from a huge page's history.

So I suggest that we need to change the data structure of the moveing logging entity to make that we can search the page moving logging record by the target page's name too.

Details

Reference: bz64184

	Subject	Repo	Branch	Lines +/-
	Allow searching the move log by destination title	mediawiki/core	master	+342 -3

Customize query in gerrit

Related Objects

Mentioned In: T214551: RevisionDeletion log does not move to new title after page move.
T152829: When displaying logs for a page, include move log entries that represent a move TO that title (not only FROM that title)
T14984: Improve filtering and search in Special:Log
T10731: Make it easy to find log actions across a page move
Mentioned Here: T14984: Improve filtering and search in Special:Log
T152829: When displaying logs for a page, include move log entries that represent a move TO that title (not only FROM that title)

Event Timeline

• bzimport raised the priority of this task from to Low.Nov 22 2014, 3:22 AM

• bzimport added a project: MediaWiki-Logevents.

• bzimport set Reference to bz64184.

• bzimport added a subscriber: Unknown Object (MLST).

Cwek created this task.Apr 21 2014, 2:55 PM

Thanks for taking the time to report this!

I'm wondering if this is the same request as in bug 12984?

(In reply to Andre Klapper from comment #1)

Thanks for taking the time to report this!

I'm wondering if this is the same request as in bug 12984?

It looks like this but it's not the same.

Maybe we can make the logging list's interface can been changed when selecting the log type which it looks like the Extension:ApiSandbox.

Liangent said that For now’s data structure,Only Insert two moving log entity which one's log_title is the source page's name and the other's log_title is the target page's name.Or Query it in the database firsthand.

Umherirrender merged a task: T47949: Move log not displayed when title is specified.Dec 28 2014, 10:12 PM

Umherirrender added subscribers: Krenair, • bzimport.

Umherirrender mentioned this in T10731: Make it easy to find log actions across a page move.Dec 29 2014, 10:14 AM

Luke081515 subscribed.Jan 9 2016, 8:29 PM

Schniggendiller subscribed.Mar 13 2016, 1:09 AM

Aklapper mentioned this in T14984: Improve filtering and search in Special:Log.Sep 5 2016, 12:18 PM

Yair_rand subscribed.May 17 2018, 10:47 PM

Would provide a useful page name history.

I mean, not altering the logs, providing a special page which would display all previous title of a given page would be sufficient.

Pols12 merged a task: T9441: Move log incomplete.Mar 19 2020, 11:45 PM

doctaxon subscribed.Mar 24 2020, 2:35 PM

• MZMcBride mentioned this in T152829: When displaying logs for a page, include move log entries that represent a move TO that title (not only FROM that title).May 1 2020, 6:49 AM

• MZMcBride subscribed.May 1 2020, 6:53 AM

Nardog subscribed.Oct 6 2020, 5:04 AM

Xaosflux subscribed.Dec 29 2021, 4:39 PM

Xaosflux added a project: Community-Wishlist-Survey-2022.Jan 10 2022, 6:19 PM

ToBeFree awarded a token.Jan 10 2022, 6:22 PM

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:13 AM

Aklapper removed subscribers: • bzimport, • wikibugs-l-list.

Change 762102 had a related patch set uploaded (by TTO; author: TTO):

[mediawiki/core@master] Allow searching the move log by destination title

https://gerrit.wikimedia.org/r/762102

gerritbot added a project: Patch-For-Review.Feb 13 2022, 9:03 AM

This task looks set to come in 10th in the Community-Wishlist-Survey-2022 ; it didn't look particularly difficult to code up, so I thought I'd have a crack.

My patch adds the move's destination title to the DB's log_search table for new moves. There is also a maintenance script to backfill this data for old move log entries so that they too can be searched.

To search for log entries regarding a page being moved to title X, you have to go specifically to the move log (as opposed to "all public logs") and enter X in a new text field which is provided for this purpose. That's not a great UX - as a user, I would expect that simply searching Special:Log for target X would return all log entries where X was either the origin or the destination of a move. However, that's not very easy to implement, and is also not what this task is asking for, so I suggest we use T152829 to track that additional enhancement.

Xaosflux awarded a token.Feb 13 2022, 2:04 PM

I'm wondering if Community-Tech might have a moment to look at this, in view of

In T66184#7706002, @TTO wrote:

This task looks set to come in 10th in the Community-Wishlist-Survey-2022

The patch is written and is almost there, just some minor issues have been flagged, but I have no time to address them.

TheresNoTime subscribed.Nov 11 2022, 2:54 PM

matej_suchanek updated the task description. (Show Details)Nov 12 2022, 9:52 AM

matej_suchanek edited projects, added Patch-Needs-Improvement; removed Patch-For-Review.

• JMcLeod_WMF moved this task from New & TBD Tickets to Needs Discussion on the Community-Tech board.Nov 21 2022, 3:13 PM

In T66184#8243480, @TTO wrote:

I'm wondering if Community-Tech might have a moment to look at this, in view of

In T66184#7706002, @TTO wrote:

This task looks set to come in 10th in the Community-Wishlist-Survey-2022

The patch is written and is almost there, just some minor issues have been flagged, but I have no time to address them.

I've rebased & am working through the comments made — thank you again for your hard work @TTO!

TheresNoTime edited projects, added Patch-For-Review; removed Patch-Needs-Improvement.Nov 21 2022, 4:27 PM

• JMcLeod_WMF set the point value for this task to 2.Nov 30 2022, 4:06 PM

TheresNoTime moved this task from Needs Discussion to Up Next (June 3-21) on the Community-Tech board.Dec 5 2022, 2:26 AM

TheresNoTime changed the point value for this task from 2 to 3.Dec 5 2022, 2:52 AM

Prefer T152829's solution. That works better in cases where the same name has been occupied by multiple pages at different points.

In T66184#8443122, @Nardog wrote:

Prefer T152829's solution. That works better in cases where the same name has been occupied by multiple pages at different points.

I've added a note to this patch to bring a reviewer's attention to your comment :-)

Func subscribed.Dec 5 2022, 3:36 PM

In T66184#8443122, @Nardog wrote:

Prefer T152829's solution. That works better in cases where the same name has been occupied by multiple pages at different points.

Please note the code-writer’s previous comment:

In T66184#7706002, @TTO wrote:

To search for log entries regarding a page being moved to title X, you have to go specifically to the move log (as opposed to "all public logs") and enter X in a new text field which is provided for this purpose. That's not a great UX - as a user, I would expect that simply searching Special:Log for target X would return all log entries where X was either the origin or the destination of a move. However, that's not very easy to implement, and is also not what this task is asking for, so I suggest we use T152829 to track that additional enhancement.

Test wiki created on Patch demo by Func86 using patch(es) linked to this task:
https://patchdemo.wmflabs.org/wikis/78fa99e8a1/w

Test wiki created on Patch demo by TheresNoTime using patch(es) linked to this task:
https://patchdemo.wmflabs.org/wikis/770dbdaea0/w

Ref https://www.mediawiki.org/wiki/MediaWiki_database_policy and https://wikitech.wikimedia.org/wiki/Schema_changes#Workflow_of_a_schema_change

From the perspective of the title search on Special:Log it would be easier to just insert a second log entry into the database. Only the first entry goes to RC (with IRC and feed) and the second is there to allow searching under the new name.
That would also allow to find the log entry from the "all public logs" selection, while the log_search solution would only work on Special:Log/move. This makes linking easier from history where a "View logs for this page" link is provided.
But that would increase the storage need for logging, where the log_search solution fits better in.

Two log entries would also bring in some problems, when looking at all logs of a performer contains often the same info. Maintenance work like revdel or suppression of bad page names needs to be done on two entries. [Edit: It must also be clear on implementation which of the both log entry gets the associated pageid/revid of the new and old page, even on redirect overwrite, redirect suppression]
I have no idea what is better, the current patch set is working and looks good.

For the protect log there is already a log entry added on move under the new name to make it possible to find the protect log for the existing (and not expired) protect of that page, to be shown when non-priviliged users want to edit a moved page. This second log on moving protected pages gives this inspiration.

Umherirrender mentioned this in T214551: RevisionDeletion log does not move to new title after page move..Feb 9 2023, 10:12 PM

TheresNoTime added a project: User-TheresNoTime.Feb 20 2023, 12:50 PM

TheresNoTime moved this task from Backlog to Patch for review on the User-TheresNoTime board.Feb 20 2023, 12:55 PM

Pppery edited projects, added Patch-Needs-Improvement; removed Patch-For-Review.Mar 19 2023, 4:17 PM

Pppery awarded a token.

Pppery subscribed.