No option to move over an existing non-redirect page in the API
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	Legoktm
	Dec 8 2012, 10:05 PM

Description

If you try to move a page over one that already exists, and have the 'delete' right, you'll get the option to delete the current page and move over it (https://toolserver.org/~betacommand/2012-12-08_165111.png).

This should be an option in the API as well for users with both the 'move' and 'delete' rights. Something like &deleteexisting=1.

Details

Reference: bz42886

Related Objects

Mentioned In: T239277: Add user right to delete single revision redirects, regardless of target, during page moves
T233435: [BUG] Deleting a page and quickly moving another page over the deleted page on a client results in bad wikidata sitelinks

Event Timeline

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

• bzimport added a project: MediaWiki-Action-API.

• bzimport set Reference to bz42886.

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

Legoktm created this task.Dec 8 2012, 10:05 PM

You can use &ignorewarnings= for that

Wasn't aware of that option, thanks. I'll go ahead and update the documentation to reflect that.

Looks like, that this param is not working for delete&move. I remind wrong.

On the other hand, the API client could just call action=delete followed by action=move to achieve the same effect. Is there a disadvantage to doing this besides that it needs an additional API query?

I can't think of any, just the fact that it requires an extra query.

I'm going to decline this, just use action=delete followed by action=move.

Xiplus subscribed.Aug 7 2019, 4:58 AM

In T44886#453340, @Anomie wrote:

On the other hand, the API client could just call action=delete followed by action=move to achieve the same effect. Is there a disadvantage to doing this besides that it needs an additional API query?

This resulted in the removal of sitelinks on Wikidata. So I think this feature will be useful.

Restricted Application added a project: Platform Engineering. · View Herald TranscriptSep 10 2019, 11:23 AM

In T44886#5478554, @A2093064 wrote:

This resulted in the removal of sitelinks on Wikidata. So I think this feature will be useful.

Does the equivalent feature in the web UI not have the same result? If not, is that not considered a bug?

In T44886#5479006, @Anomie wrote:

Does the equivalent feature in the web UI not have the same result? If not, is that not considered a bug?

Moving over page in web UI doesn't trigger removal of sitelink. I don't think this is a bug. For example, in a history merge case.

WDoranWMF moved this task from Triage Meeting Inbox to Tracking/Watching on the Platform Engineering board.Sep 10 2019, 6:12 PM

Addshore added a project: Wikidata.Sep 19 2019, 8:40 PM

Addshore updated the task description. (Show Details)

Addshore moved this task from incoming to monitoring on the Wikidata board.

Addshore edited subscribers, added: Lydia_Pintscher, • alaa_wmde; removed: • wikibugs-l-list.

In T44886#5478554, @A2093064 wrote:

In T44886#453340, @Anomie wrote:

On the other hand, the API client could just call action=delete followed by action=move to achieve the same effect. Is there a disadvantage to doing this besides that it needs an additional API query?

This resulted in the removal of sitelinks on Wikidata. So I think this feature will be useful.

This sounds like a case that we need to fix in Wikibase.
Currently the delete and move sitelink alterations are done in jobs, and i believe it is still possible that these job will be executed in the wrong order.

@A2093064 do you have an example edit / move that has been made and links to the edits it caused on wikidata that we could look at and confirm?
Then we can probably close this as it was closed in T44886#1050673 and open a new ticket for the wikibase bug caused by quickly performing a delete then a move on a client.