daniel added a comment. In https://phabricator.wikimedia.org/T71167#1216284, @Addshore wrote:
> Personally I think the maxResolutionDepth of EntityRedirectResolvingDecorator > should be set to something greater than 1, perhaps 5? > This will avoid the issue described above and shouldn't impact anything > greatly. It should be $wgMaxRedirects, which is 1 per default and on all WMF sites, afaik. Would be interesting to know if there would be any issues with increasing it. However, I see no reason to treat wikibase items specially here. Item redirects should behave e3xactly as all redirects do (and this is currently the case, as far as I can tell). > The alternative would be on creating a redirect, find everything that is > already redirecting to the itemid that you are about to redirect to somewhere > else and also change those.... That's what $wgFixDoubleRedirects controls. It's disabled on WMF sites I think. The documentation says: //"Fix double redirects after a page move. Tends to conflict with page move vandalism, use only on a private wiki."// It would be nice if RedirectCreationInteractor would optionally fix double redirects, if $wgFixDoubleRedirects is set. That way, Special:MergeItems would behave in a way that is consistent with what Special:MovePage does. TASK DETAIL https://phabricator.wikimedia.org/T71167 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel Cc: Bugreporter, Addshore, Ricordisamoa, Multichill, Liuxinyu970226, Lydia_Pintscher, Stryn, daniel, JohnLewis, Wikidata-bugs, aude, Malyacko, P.Copp _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
