In T283626#7122513, @Lucas_Werkmeister_WMDE wrote:

As the issua affects thousands of pages, it deserves a higher priority.

Thanks for the deployment. Does this instantly affect the scoring interface?

Yes, as the message is also displayed in the protection log entry, it would be great to create a new system message to separate linked and unlinked versions.

The problem is that, once the change is made, the summary is not displayed properly in protection log.

I can see that edits resulting in content that is the same as an older version are being tagged this way, as you can see here. These edits were made by not using the undo button on the history page.

Here is a more complex example. As far as I can see, rewriting this in pure application logic requires lots of developer work, if such an implementation is feasible at all.

It seems that some of my queries on Quarry will be severely affected by this change. What can be done for cases like this?

@Huji What do you mean? As far as I can see, the tool works correctly if you select a namespace,

@Akoopal Yes, you may add me as a maintainer if you like.

@Huji The tool is up and running here.

The community consensus can be found here.

In T247330#5974783, @Aklapper wrote:

@Superyetkin: Do you plan to follow T247330#5957545 and bring this up on meta and notify trwikinews?

In T248747#6007377, @Urbanecm wrote:

Let me know if this is what you want. I'd also need an on-wiki discussion about this.

Best,
Martin

In T247330#5957272, @Reedy wrote:

Though, I find it slightly amusing "community consensus" for closing trwikinews has been done on trwiki...

Is there any estimate as to when we will start using this database on replica servers?

Is there any chance we can have the features deployed before completing the translations? This may take a while on our side.

Change undone, thanks.

The issue persists on trwiki.

It is T221679

The same issue, which was reported earlier, persists on trwiki. I suggest tracking this task with a higher priority level.

I have just made the tool functional again by reusing the source code and fixing minor bugs. It is available here.

Could you please run it for trwiki? Thanks.

The problem persists. Any plans to have this resolved? Any chance to trigger the recount manually?

@Aklapper, I think the applied patch having failed changes the situation. The problem persists and needs to be worked on more closely.

The patch does not seem to have any positive effect on trwiki. The call {{PAGESINCATEGORY:Vikipedi silinecek sayfalar}}
returns 12 while the category is empty (as of May 3, 2019).

{{PAGESINCATEGORY:Geçmişleri birleştirilecek maddeler}} returns 13 on trwiki.

Is the source code available?

What needs to be done to fix this issue? A patch?

Is this aimed at Twitter only? It would be a good idea to create a tool that generates a short URL to a page listing helpful information about wiki pages.

Where is the repository located?

As far as I can see, we need to implement a custom "LogFormatter" instance to make this happen. Is that right?

Where is the codebase for Erwin's tools located? I would be interested in joining the development team.

I would be interested in building a tool for this in case there is some hesitation to do the job on Mediawiki.

I can go ahead with this if there is an agreement on the proposed layout.

Any updates?

The functionality has arrived for wikis but the commit does not appear in the release notes. Is something wrong?

The related gadget page has been updated, with no visible effect on functionality. Regarding the fact that the issue is not linited to a number of small wikis, it may need to be dealt with under a Phabricator ticket, possibly attracting developers familiar with the script.

I do not think it is too late for such a change. Affected pages can be fixed before any deployment action is taken.

Patch uploaded at https://gerrit.wikimedia.org/r/#/c/428129/

Code review in progress?

Okay, I have updated the templates and everything seems to work fine now. Thanks.

I think we can move forward with this. Thanks.

I have just started a discussion here. We will move forward with this according to the comments appearing there.

I would be interested in helping you out with enabling this feature on trwiki. Is there anything we (the community) can do at the moment?

Thanks, removing the redundant code solved the issue.

How to fix it?

The community demands that the config change be made. Thanks.

Any chance to recover data?

I do not think it is a good idea to throw an exception when a project does not exist. databasePrepare() in LabsHelper.php must change. Having some kind of error "pipeline" would also help notify users something is going wrong.