Last modified: 2014-11-07 11:43:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58457, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56457 - After moving a page if the item has conflict in wikidata wikidataClient leave items without error
After moving a page if the item has conflict in wikidata wikidataClient leave...
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
WikidataClient (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Wikidata bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-01 07:23 UTC by reza1615
Modified: 2014-11-07 11:43 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description reza1615 2013-11-01 07:23:29 UTC
In wikipedia page foo has item in wikidata When we move page foo to foo2
if items have conflict in wikidata. wikidataClient leave items without error so page is moved in wikipedia but it's items didn't update or changed.
this problem makes leave langlinks in redirect page!

Solution:
In my opinion we should add an alarm which popup and tells to user that the langlink didn't move.

example:
en:foo (item:Q123) > en:foo2 (it had item Q456)
after moving en:foo to en:foo2 because of second item wikidataClient can not move langlink from Q123 to Q456 so it leave the langlink in en:foo (item:Q123)!
Comment 1 Marius Hoch 2013-11-06 17:02:04 UTC
This will only occur if we already have a redirect or a deleted page with an item (which shouldn't happen, but does so in the real world).
Comment 2 Lydia Pintscher 2014-11-07 11:38:27 UTC
What's our realistic chance of fixing this? How much impact does it have? How hard would it be to fix?
Comment 3 Marius Hoch 2014-11-07 11:41:49 UTC
The impact is low (this shouldn't actually occur at all, it only does if we start with invalid data).

Fixing this would require binding against a cross wiki version of Echo (which AFAIK doesn't even exist yet) or building an own notification system of some sort (this is needed as these events are asynchronous).
Comment 4 Lydia Pintscher 2014-11-07 11:43:28 UTC
Ok then let's be honest with ourselves and admit that it is not going to happen. Sorry.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links