MediaWiki talk:Gadget-Merge.js/Archive 2

Bye bye, old code

To make this action a milestone, we should archive the old talk page :-)

The next thing on the to-do list could be now an interaction between the gadget and backlinks. My proposal is to have a checkbox with: "After deleting ask a bot to move backlinks". After/before deleting (thus sysops only) the gadget would check if there are some backlinks, and if yes, the gadget makes a request on the page User:BeneBot*/movelinks.js. Matěj Suchánek (talk) 21:06, 13 June 2014 (UTC)

Hmm. Probably just for admins is not a good idea. Currently am doing some code and UI clean up so it will help its readability and development. BTW, doesn't stream deletion help on this case? –ebraminio^talk 12:35, 14 June 2014 (UTC)

User:Ricordisamoa/StreamDelete: There are five columns: sitelinks, claims, labels, descriptions, aliases... but no backlinks. Matěj Suchánek (talk) 12:49, 14 June 2014 (UTC)

@User:Ricordisamoa: Hi. Couldn't StreamDelete support backlinks or send backlink move requests to BeneBot*? –ebraminio^talk 12:09, 16 June 2014 (UTC)

@Ebraminio: StreamDelete only uses Lua, which AFAIK does not support backlinks yet. That would need JavaScript, which I will use in an interactive RfD script (coming in the next decades). --Ricordisamoa 22:40, 30 June 2014 (UTC)

@Matěj Suchánek:: I added such feature on MediaWiki:Gadget-RfDHelper.js so you will see a button for quick moving backlinks request on RfD near count of backlinks. –ebraminio^talk 13:03, 21 June 2014 (UTC)

I am not sure if StreamDelete is still necessary since most merges should end in a redirect in stead of a deletion. Perhaps this option be removed. Kind regards, Lymantria (talk) 05:31, 28 August 2014 (UTC)

Arabic translation

{{Edit request}}

      'ar': {
        confilictMessage: 'ثمة خطب في ',
        confilictWithMessage: 'مع',
        deleteOption: ' حاول بعد الدمج حذف المواد الإضافية تلقائيا (للإداريين فقط)',
        deleting: 'يحذف...',
        loadingMergeDestination: 'تحميل وجهة الدمج...',
        lowestQid: 'ادمج دائما تحت المعرف ذي العدد الأصغر',
        merge: 'دمج',
        mergePendingNotification: 'أداة الدمج تعمل.<br/>يمكنك الآن الاطلاع على المادة الأخرى.',
        mergeProcess: 'ادمج الآن',
        mergeThisItem: 'ادمج هذه المادة',
        mergeWithInput: 'ادمج مع:',
        mergeWithProgress: 'يدمج مع...',
        mergeWizard: 'أداة الدمج',
        pleaseWait: 'انتظار...',
        postpone: 'تأجيل',
        postponeTitle: 'خزن معرف هذه المادة وأجل الدمج',
        processPostponed: 'أجر الدمج المؤجل',
        requestDeletion: 'اطلب حذف المادة الإضافية في صفحة طلب',
        requestingDeletion: 'يطلب الحذف...',
        requestingStreamDeletion: 'أضف لقائمة الحذف...',
        sendingToRfd: 'يرسل إلى صفحة طلبات الحذف...',
        streamDelete: 'طلب إضافة المادة $1لقائمة الحذف$2 (تجريبي)',
        unwatchOption: 'حذف المادة المدمجة من قائمة المراقبة (إن كان فيها)',
        unwatching: 'يحذف من القائمة...'
      },

Shukran--Zack (talk) 00:25, 26 July 2014 (UTC)

 Done (diff) --Fomafix (talk) 08:24, 26 July 2014 (UTC)

Error while "Requesting Stream Deletion...": http

I just have got this message when I tried to merge Q9363895 into Q2357982. Jdx (talk) 07:27, 3 August 2014 (UTC)

The same error occurred when I tried to merge Q11795307 into Q5380913. Jdx (talk) 11:48, 3 August 2014 (UTC)

Merge failed

Q9720654, Category:University of Bologna (Q8816880)--Oursana (talk) 07:41, 5 August 2014 (UTC)

Error

I couldn't merge Q627232 with Q15981562 --BokicaK (talk) 14:29, 13 August 2014 (UTC)

Merge failed

Tried to merge Q9797809 into Q16004552. --Jklamo (talk) 16:00, 13 August 2014 (UTC)

No deletion request

Hi. I tried to merge Q6886627 with Q5836198. The tool merged them but it didn't submit any deletion request for the empty item here. MRG90 (talk) 08:33, 19 August 2014 (UTC)

I no longer have that problem. MRG90 (talk) 10:04, 19 August 2014 (UTC)

Trouble with merge

I received an error while merging Q17522215 into Q16169064 Jane023 (talk) 13:23, 19 August 2014 (UTC)

The merge happened correctly, I have deleted the first item. --Ricordisamoa 16:04, 19 August 2014 (UTC)

Merge error

Error merging Q2502369 and Q1678885. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:54, 19 August 2014 (UTC)

wbcreateredirect

So, redirect creation should be used instead item deletion and WD:RfD system? Is it possible to remove them from the code and make wbcreateredirect default action? –ebraminio^talk 13:19, 20 August 2014 (UTC)

(cc: User:Ricordisamoa, User:Fomafix) WDYT? –ebraminio^talk 13:21, 20 August 2014 (UTC)

Technically "merge without delete" is necessary to create a redirect. You can't create a redirect if item isn't empty. --ValterVB (talk) 14:00, 20 August 2014 (UTC)

ValterVB How about removing sysop delete and deletion request functionalities at once? –ebraminio^talk 15:15, 20 August 2014 (UTC)

@Ebraminio: Maybe is necessary start a discussion about redirect. When we can use merge with delete and when we can use merge with redirect? I report this discussion to the bar and to the Administrators' noticeboard. --ValterVB (talk) 15:28, 20 August 2014 (UTC)

I don't believe MediaWiki's delete feature is suitable for Wikibase. Why would you want to delete an item, except in cases when it contains libelous information? Vogone (talk) 15:38, 20 August 2014 (UTC)

I haven't a real reason, but I have thinked that is better a little discussione on it. If there aren't opposition we can transform this gadget to create only redirect and exclude all the part about RfD --ValterVB (talk) 15:52, 20 August 2014 (UTC)

Rename it to WD:RfR (for Redirect). All those action should be closely monitored. --Succu (talk) 17:54, 20 August 2014 (UTC) PS: Why should items with zero statements become a redirect?

Redirects have negative side: its increase complexity of data clients. Client can not simple compare Q-ids. It must request wikibase every time. So I think it is better delete redirects after fixing links to it. — Ivan A. Krestinin (talk) 20:11, 20 August 2014 (UTC)

No please don't! It is extremely important that our identifiers can be seen as stable. If someone uses Q1234 now they need to be able to do that in 5 years still and end up at something that represents at least roughly the same concept. --Lydia Pintscher (WMDE) (talk) 10:23, 21 August 2014 (UTC)

It is correct point. Deleting is not so important part of my think. It is enough to fix links to redirects. Interesting question for bot implementation: how to query list of redirects created during last 2-3 hours? — Ivan A. Krestinin (talk) 18:20, 21 August 2014 (UTC)

I would even avoid fixing the links to a redirect. It makes it very difficult to revert a wrong merge, while the changes to the two items merged could be reverted easily (hope one can revert a redirect back to its original content), it is a tedious task to check every incoming link whether it belongs to the merge target or the merge source. Ahoerstemeier (talk) 12:50, 22 August 2014 (UTC)

Yes, this is negative point of redirects fixing. But this is not very often situation. Usually time lag is enough to avoid the most such cases. Increasing complexity of every data processing algorithm is more worse. — Ivan A. Krestinin (talk) 17:55, 22 August 2014 (UTC)

Then we need a tool to list all the redirect in ns0, because Special:ListRedirects don't is useful --ValterVB (talk) 20:31, 20 August 2014 (UTC)

Edit label "redirect created" can be used as temporary approach. — Ivan A. Krestinin (talk) 21:35, 20 August 2014 (UTC)

I have created Special:AbuseFilter/50. Should we exclude some (or all but main) namespaces? What tag should be added to these edits? ("redirect created"? "item redirect"?) whym (talk) 23:24, 21 August 2014 (UTC)

That filter does not seem to work properly. Lymantria (talk) 19:39, 27 August 2014 (UTC) -- Tried to fix it. Lymantria (talk) 05:36, 28 August 2014 (UTC) -- Hmm, that didn't help. Lymantria (talk) 05:42, 28 August 2014 (UTC)

Hey guys, deleting redirects is the opposite of what we want to achieve with wikidata, which is creating stable identifiers. Therefore, do not delete any redirects. -- Bene* ^t_a^l_k 05:44, 28 August 2014 (UTC)

@Lymantria: Special:AbuseFilter/history/50/diff/623/625. Matěj Suchánek (talk) 07:34, 28 August 2014 (UTC)

@Matěj Suchánek:: It still doesn't find redirect-creations in main namespace. I tried to fixes, one obviously created many false positives, the other has the same problems as the original. :s. Lymantria (talk) 10:49, 28 August 2014 (UTC)

@ValterVB: Would http://quarry.wmflabs.org/query/389 be useful? (it doesn't have fancy hyperlinks, though.) whym (talk) 12:20, 29 August 2014 (UTC)

@Ivan A. Krestinin: I really don't get your point. Redirects are designed to work well and won't create any performance issues etc. so what's the problem with having them? Please leave the redirects for the reasons ValterVB mentioned. Otherwise it'll be impossible to fight vandalism and revert bad merges. -- Bene* ^t_a^l_k¢

Personally, I think deletion should remain an option (useful, for example, when an item has been created a few minutes before being merged), with redirect creation being "just another option". --Ricordisamoa 22:46, 31 August 2014 (UTC)

But why? Redirects don't hurt and providing deletion as an alternative only provides another cause for errors. Items should only be deleted in cases of spam or personal attacks etc but not when they get merged. -- Bene* ^t_a^l_k 10:38, 1 September 2014 (UTC)

Merge failed

https://www.wikidata.org/wiki/Q3141064 is superfluos. Merge with https://www.wikidata.org/wiki/Q3141064 failed. Dyveldi (talk) 22:47, 22 August 2014 (UTC)

error merging Q1641062 and Q2915989

--Hokanomono (talk) 20:10, 25 August 2014 (UTC)

it translation update

				confilictMessage: 'Rilevato un conflitto in ',
				confilictWithMessage: 'con',
				createRedirect: 'Crea un redirect',
				creatingRedirect: 'Creazione del redirect...',
				deleteOption: 'Cancella automaticamente gli elementi svuotati dopo l\'unione (solo amministratori)',
				deleting: 'Cancellazione...',
				loadingMergeDestination: 'Caricamento della destinazione...',
				lowestQid: 'Unisci sempre con l\'elemento con il più piccolo Qid',
				merge: 'Unione',
				mergePendingNotification: 'Merge.js è stato avviato.<br/>Adesso vai sulla pagina dell\'altro elemento.',
				mergeProcess: 'Effettua l\'unione adesso',
				mergeThisItem: 'Unisci questo elemento',
				mergeWithInput: 'Unisci con:',
				mergeWithProgress: 'Unione con l\'elemento...',
				mergeWizard: 'Unione guidata',
				pleaseWait: 'Attendere...',
				postpone: 'Rimanda a dopo',
				postponeTitle: 'Memorizza l\'id di questo elemento e rimanda a dopo l\'unione',
				processPostponed: 'Elabora l\'unione rimandata',
				requestDeletion: 'Richiedi la cancellazione degli elementi svuotati',
				requestingDeletion: 'Richiesta di cancellazione...',
				requestingStreamDeletion: 'Richiesta di cancellazione in Stream...',
				sendingToRfd: 'Inserimento fra le richieste di cancellazione...',
				streamDelete: 'Richiedi la $1Cancellazione in Stream$2 per questo elemento (sperimentale)',
				unwatchOption: 'Rimuovi gli elementi uniti dagli osservati speciali (se presenti)',
				unwatching: 'Rimozione dagli osservati speciali...'

Thanks in advance. --FRacco (talk) 22:35, 25 August 2014 (UTC)

@FRacco:  Done: [1] – thank you! James F. (talk) 21:24, 1 September 2014 (UTC)

Error merging Q8880570 and Q10037520

Not quite sure why. Error message was:

Error while "Merge with: Q8880570": http

James F. (talk) 21:19, 1 September 2014 (UTC)

Please update zh-hans

{{Editprotected}} Please add:

				createRedirect: '创建重定向',
				creatingRedirect: '创建重定向中…',

--Liuxinyu970226 (talk) 09:49, 4 September 2014 (UTC)

 Done Matěj Suchánek (talk) 10:35, 4 September 2014 (UTC)

Stripping blank spaces around input Qid

{{Editprotected}}

Hi, I generally copy-paste Qid in the merge dialog and often accidentally paste an extra space before or after the Qid, which causes message "Currently only "Qid" is a valid input" to be displayed... I think it can be fixed easily at line 812: replace

var itemsNames = [$('#merge-items').val(), itemId.toUpperCase()],

with

var itemsNames = [$.trim($('#merge-items').val()), $.trim(itemId.toUpperCase())],

I could not test, please double-check - for example you may test by merging Category:Serbian film editors (Q16500660) into Category:Serbian film editors (Q8731250)... :)

Thanks - LaddΩ chat ;) 23:54, 6 September 2014 (UTC)

I can not find a situation where are spaces around the Qid. Where do you copy wrapping spaces? --Fomafix (talk) 10:06, 7 September 2014 (UTC)

Mainly from User:Byrial/countrymerge/fr-en. LaddΩ chat ;) 16:07, 7 September 2014 (UTC)

@Fomafix: Hi, what is the status of this request? LaddΩ chat ;) 02:19, 18 September 2014 (UTC)

I added $.trim(). (diff) --Fomafix (talk) 10:56, 18 September 2014 (UTC)

Y Works great! thanks - LaddΩ chat ;) 21:59, 18 September 2014 (UTC)

Delete/redirect

This gedget has been reverted into deleting rather than redirecting the merged item. But redirecting is much better. Is the redirect function really not function, or can we soon put it back to redirects rather than deletions ? --Zolo (talk) 08:56, 7 September 2014 (UTC)

@Zolo: You can select Redirect or Delete. --ValterVB (talk) 09:37, 7 September 2014 (UTC)

@ValterVB:, yes sorry I had just seen that someone had deleted an item that should have been redirected, so I thought it had been disabled. I'd say we can geet rid of the deletion option though. When items should be merged, once should be redirected. --Zolo (talk) 12:57, 7 September 2014 (UTC)

I suggest we start by putting the merge option at the top of the dialog list and the delete option at the bottom. LaddΩ chat ;) 16:09, 7 September 2014 (UTC)

Yes, agree. -- Bene* ^t_a^l_k 21:17, 8 September 2014 (UTC)

@Zolo, ValterVB, Laddo, Bene*:  Done in this edit. Do you think we should also change the language around "Request deletion for extra item on RfD" to something like "Request deletion for extra item on RfD (if recently created)"? James F. (talk) 23:43, 8 September 2014 (UTC)

Thanks. Possibly, but to me this is not really necessary to delete even recently created items (I would say that the only items that need to be deleted is those that inextricably mixed up two concepts). --Zolo (talk) 13:02, 9 September 2014 (UTC)

Thanks, and no, isn't necessary change the sentence. --ValterVB (talk) 17:43, 9 September 2014 (UTC)

I also don't think recently created items should be deleted but you might also change the order of the if clauses and put the redirect option to the top so that it will be used on favor of deleting if both are checked. -- Bene* ^t_a^l_k 18:24, 9 September 2014 (UTC)

We cuurently have 3 deletion options. That does not seem necessary. A binary redirect/delete choice would look simpler. Can we at least remove thise "stream deletion" option ? (Well no choice at all, just redirect would be all-round better to me, but I guess we cannot do that until the RFC about redirects is settled). --Zolo (talk) 22:19, 8 November 2014 (UTC)

Error report

It worked the second time, but since the script told me to report it, I'm reporting.

The page I wanted to merge: Q10022373. Destination: Q9677361. --Moscow Connection (talk) 21:43, 9 September 2014 (UTC)

Attempt to merge Q9588925 and Q8575560 failed

Hi, I tried merging these two duplicate categories for the Komi language using this gadget, but it returned an error and asked me to leave a note here. Thanks for any and all help. -Yupik (talk) 10:09, 13 September 2014 (UTC)

Merging these same values with different sources

With merging two items with some property having these same values, but with different sources - after merge finishing, these values is duplicated. See example Q4266922 (coordinates is duplicated). In my opinion, the correct way is as a result there is a single value, which has two sources of. --Kaganer (talk) 11:20, 5 November 2014 (UTC)

@Kaganer: According to Special:AbuseFilter/examine/171223343 (maybe you can't see it) those values were not same but they were almost same. Compare 49.38055556 24.77277778 0.00027777777777778 and 49.380555555556 24.772777777778 0.00027777777777778. I believe that if they had been same, they would have been merged correctly. Just a note that this would be an issue for developers rather than in the gadget. Matěj Suchánek (talk) 14:34, 5 November 2014 (UTC)

Thanks, I already suspected it ;) This extreme precision, in my opinion. Maybe needed addition dialog for comparision of coord. values and/or select one from these... --Kaganer (talk) 21:10, 5 November 2014 (UTC)

Make Create redirect permanently checked

According to WD:PC#Merging without creating a redirect is ugly the redirect should always be created. Please apply this edit, which makes the Create redirect checkbox permanently checked. Petr Matas 11:08, 28 November 2014 (UTC)

Now it is checked by default, I suppose this is resolved. Matěj Suchánek (talk) 11:43, 14 December 2014 (UTC)

Only partialy. The disabled: fixedValue !== undefined line has not been applied, so the user can still uncheck the checkbox. Petr Matas 12:05, 14 December 2014 (UTC)

Then one may see no reason to have the option at all... Matěj Suchánek (talk) 12:33, 14 December 2014 (UTC)

The reason is to spare the users wondering what happened to the option and whether the redirect is going to be created. Petr Matas 12:39, 14 December 2014 (UTC)

 Done --Pasleim (talk) 07:43, 16 December 2014 (UTC)

remove deletion options

Per Wikidata:Requests for comment/Redirect vs. deletion, please remove the following three options

• Request deletion for extra item on RfD
• Request StreamDeletion for this item (experimental)
• Try to automatically delete extra item after merge (only admins)

This way we prevent people who are not aware of the policy change from accidentally deleting things or nominating them for deletion. Multichill (talk) 21:51, 3 December 2014 (UTC)

Trying but i am not good at javascript. I will try again later--DangSunM (talk) 15:59, 4 December 2014 (UTC)

{{Edit request}}

This edit contains the changes to be applied. Petr Matas 16:41, 4 December 2014 (UTC)

Please see Wikidata:Administrators'_noticeboard#Close_a_RFC. There's sometimes reason to delete the item after the merge. --Stryn (talk) 18:09, 4 December 2014 (UTC)

Thanks Petr Matas, applied. If someone wants to make a nifty version that checks for the age of the item and shows the option to delete if the item is younger than 24hours: Be my guest, I'm more than happy to apply that change. Multichill (talk) 18:34, 4 December 2014 (UTC)

Seems to contain a bug, reverted. Multichill (talk) 18:43, 4 December 2014 (UTC)

@Multichill: It seems that you applied a different edit, by 분당선M. Additionally, Matěj Suchánek was doing some changes at the same time. Petr Matas 00:56, 5 December 2014 (UTC)

 Done Now, This verson actually works! and i think we have to use the RD gadget to request deletion for below 24 hrs. or can just restore delete function only later on. --DangSunM (talk) 04:26, 5 December 2014 (UTC)

For testing, please check Q5640197 and Q5821400--DangSunM (talk) 04:27, 5 December 2014 (UTC)

The only option that is not related to deletion is "redirect to smallest Qid" and I do not see any harm it always redirecting to smallest Qid without giving any choice to the user. If we remove the deletion options, I think we could remove other options and replace them with a confirmation message like "you are going to move bla and bleble, are you sure that they are exactly about the same topic ?"--Zolo (talk) 07:20, 5 December 2014 (UTC)

Before, it was recommended to do smallest. but for now I don't know. Not defult check. so leave as a option for who prefer to merge into smallest Qid.--DangSunM (talk) 15:19, 7 December 2014 (UTC)

I do not see any reason for letting that to the discretionary taste of the merger. If there are cases where merging item into the smallest ID, it should be documented somewhere, but I doubt there are. It really sounds simpler, more user-friendly and more fool-proof to remove all options from the input box, so that no one needs to bother about all those things. --Zolo (talk) 13:17, 14 December 2014 (UTC)

The "create a redirect" option could probably be checked by default! Also, Help:Merge needs updating (in all languages...) Place Clichy (talk) 09:42, 5 December 2014 (UTC)

Merge gadget looses label

I just noticed that if you merge two items and both have a label in the same language that one of the labels gets dropped. If the labels are different, the second one should be added as an alias. Especially for people where you have a lot of name variations, this is important. Multichill (talk) 19:44, 5 December 2014 (UTC)

This is phab:T67990. Matěj Suchánek (talk) 19:49, 5 December 2014 (UTC)

Please see my question on phab:T67990 ·addshore· ^{talk to me!} 11:23, 7 December 2014 (UTC)

Make the direction of the merging clear

{{Edit request}} Please apply this edit, which changes one label in the dialog to clarify which of the two items is the merge target. It also makes sure that jStorage, which is required by the script, is always loaded. During debugging it turned out that this is not always the case... Petr Matas 19:13, 14 December 2014 (UTC) Update: Merge summary label clarified as well. Petr Matas 19:37, 14 December 2014 (UTC)

 Support Well done, but I will wait for others. Matěj Suchánek (talk) 19:21, 14 December 2014 (UTC)

This phrasing only makes sense when the active item is merged to the item provided in the input box. It may not always be the case when the "merge to smallest Qid" option is checked. As mentioned above, I am for removing this option, and this appears to be a precondition for chancing the phrasing. I do not think which item is kept matters very much, but that always redirecting to the smallest Qid is better, as this is the most likely to be used in other items and in external websites, and for some purposes linking to a "real" item instead of a redirect may be better. If we always redirect the highest Qid, then the phrasing should not be changed. --Zolo (talk) 19:57, 14 December 2014 (UTC)

 Not done per Zolo. Merge summary label clarification has been applied separately. Petr Matas 09:25, 16 December 2014 (UTC)

Remove "create a redirect" option

I see that the delete options have been removed but the "create a redirect" option still exists. That alows to merge items without either deleting or creating a redirect, and is the worst possible option. Can someone disable the possiblity of merging without redirects ? --Zolo (talk) 19:59, 14 December 2014 (UTC)

The edit request in #Make Create redirect permanently checked solves this. Petr Matas 20:23, 14 December 2014 (UTC)

[not] Always, always merge into the older item

It has been proposed that the user should not be allowed to merge into the item with the higher Qid (see Zolo's comments in the previous sections). To make clear to the user, what is going to happen, I propose to make the corresponding checkbox permanently checked and disallow the user to change that. To achieve that, the following changes should be applied:

1. Add the line disabled: fixedValue !== undefined as requested in #Make Create redirect permanently checked
2. Change
   createCheckbox('merge-always-lowest-id', messages.lowestQid),
   to
   createCheckbox('merge-always-lowest-id', messages.lowestQid, true),

Remember, we don't need to hurry with removing things (checkboxes in this case). Petr Matas 20:54, 14 December 2014 (UTC)

 Support I agree. --Epìdosis 21:01, 14 December 2014 (UTC)

Petr, thanks, I wanted to try your code but the your when editing the page there is a message telling to check the code with http://jslint.com/ and when I try it with your version there are many more errors than with the current script. As I do not speak javascript, I prefer to let another admin see if this is ok. --Zolo (talk) 18:17, 15 December 2014 (UTC)

I have fixed the JSLint errors, here is the resulting diff to be applied, which includes all my changes except the one for the "Merge with:" label. Petr Matas 00:14, 16 December 2014 (UTC)

 Done --Pasleim (talk) 07:42, 16 December 2014 (UTC)

Thank you very much. Petr Matas 09:21, 16 December 2014 (UTC)

Given that some of the newer items might be more frequently used, would you change it back to at least allow to uncheck this? --- Jura 06:31, 17 December 2014 (UTC)

{{Edit request}}

Patch. Petr Matas 06:55, 17 December 2014 (UTC). Update: Petr Matas 08:26, 17 December 2014 (UTC)

 Done I will post my suggestions to a new section. Matěj Suchánek (talk) 09:33, 17 December 2014 (UTC)

Thanks for your thorough review. :) Petr Matas 22:01, 17 December 2014 (UTC)

I think it is better to preserve the item with the longest history (i.e., the largest number of edits in the history) and redirect the other one. Sometimes I edit extensively on an item (labels, descriptions etc.) and only later merge it with another item, which may accidentally have a lower Q-id. People should be able to look up the edit history of an item easily. Bever (talk) 23:15, 9 March 2015 (UTC)

For example compare this edit history with this history. Bever (talk) 23:19, 9 March 2015 (UTC)

Easier access to the Postpone functionality

This edit adds the Postpone action also as an item in the "More" drop-down menu. Please apply it. Petr Matas 22:02, 14 December 2014 (UTC)

 Done --Pasleim (talk) 07:43, 16 December 2014 (UTC)

Portuguese translation

Hi!

I would like to add these translations for (Brazilian) Portuguese:

      'pt-br': {
        confilictMessage: 'Um conflito detectado em ',
        confilictWithMessage: 'com',
        createRedirect: 'Criar um redirecionamento',
        creatingRedirect: 'Criando um redirecionamento...',
        deleteOption: 'Tentar eliminar o item extra automaticamente depois da fusão (apenas administradores)',
        deleting: 'Eliminando...',
        loadingMergeDestination: 'Carregando o destino da fusão...',
        lowestQid: 'Sempre fundir no item com o menor Qid',
        merge: 'Fundir',
        mergePendingNotification: 'Merge.js foi iniciado.<br/>Agora você pode focar o seu navegador no outro item.',
        mergeProcess: 'Processar a fusão agora',
        mergeThisItem: 'Fundir este item',
        mergeWithInput: 'Fundir com:',
        mergeWithProgress: 'Fundir com...',
        mergeWizard: 'Assistente de fusões',
        pleaseWait: 'Por favor espere...',
        postpone: 'Adiar',
        postponeTitle: 'Armazenar o id deste item e adiar a fusão',
        processPostponed: 'processar a fusão adiada',
        requestDeletion: 'Solicitar a eliminação do item extra em um RfD',
        requestingDeletion: 'Solicitando a eliminação...',
        requestingStreamDeletion: 'Solicitando uma eliminação em stream...',
        sendingToRfd: 'Enviando para RfD...',
        streamDelete: 'Solicitar $1StreamDeletion$2 para este item (experimental)',
        unwatchOption: 'Remover item fundido de sua lista de páginas vigiadas (se estiver vigiando)',
        unwatching: 'Removendo da lista de páginas vigiadas...'
      },

Helder 10:56, 15 December 2014 (UTC)

 Done (diff) --Fomafix (talk) 16:51, 15 December 2014 (UTC)

Does it work for non Brazilian Portuguese ? Given that mediawiki's fallback is from pt-br to pt rather than the other way around, it would be better to have "pt" than "pt-br". --Zolo (talk) 18:09, 15 December 2014 (UTC)

The fallback chain (mw.language.getFallbackLanguageChain()) for pt is ["pt", "pt-br", "en"] and the fallback chain for pt-br is ["pt-br", "pt", "en"]. So it works for non Brazilian Portuguese.

But it would be better to use pt and add a separate section with pt-br where the messages differ in Brazilian Portuguese. --Fomafix (talk) 10:58, 16 December 2014 (UTC)

Oh ok, last time I checked fallbackcain were monodirectional. --Zolo (talk) 11:57, 16 December 2014 (UTC)

mis-merged items

sorry I made a mistake and merged the lower number into the higher number - can someone pls fix? Aegidius Sadeler (Q5481491) and Aegidius Sadeler (Q1297898). Thx Jane023 (talk) 12:22, 16 December 2014 (UTC)

No, it's been done in the correct way. The Merge gadget is more clever now :) Petr Matas 12:36, 16 December 2014 (UTC)

OK thanks! Glad to see the gadget making this decision for me, I know I have made this mistake in the past as well. Jane023 (talk) 13:09, 16 December 2014 (UTC)

Improve Czech translation

{{Edit request}} Please change

unwatchOption: 'Odstranit slučované položky ze sledovaných stránek (jsou-li sledovány)',

to

unwatchOption: 'Odstranit vyprázdněnou položku z vašich sledovaných stránek (je-li sledována)',

Petr Matas 12:42, 16 December 2014 (UTC)

 Done (diff) --Fomafix (talk) 12:48, 16 December 2014 (UTC)

Ideas

• Not used messages – do we have to keep them? Matěj Suchánek (talk) 09:45, 17 December 2014 (UTC)

  I would leave them in place for a few weeks and remove them when it becomes clear that the removed options are not going to be returned. Petr Matas 22:13, 17 December 2014 (UTC)

• lowestQid: – is the word Always needed? Matěj Suchánek (talk) 09:45, 17 December 2014 (UTC)

  No, it's superfluous. Petr Matas 22:13, 17 December 2014 (UTC)

• We should encourage users to translate the gadget (link or text like "You can translate the gadget"). Matěj Suchánek (talk) 09:45, 17 December 2014 (UTC)

  Good idea, but first we should prepare a translation how-to, which we are going to link to. Petr Matas 22:13, 17 December 2014 (UTC)

  Are there any gadgets, which make use of the translation system? Petr Matas 09:32, 18 December 2014 (UTC)

Resolve redirected sitelinks

Take Q2795323. This was an empty item with just one sitelink. This sitelink is a redirect at the Dutch Wikipedia. The target article of the redirect is connected with Dendrocoelum longipenis (Q2595612) Would be nice if this gadget would understand this and would let me merge Q2795323 with 2595612 and would just drop the sitelink to the redirect. Multichill (talk) 21:27, 20 December 2014 (UTC)

It is not a good idea to resolve links to redirects automatically. Some redirects describe different objects and there are separate items for the redirect and the target. --Fomafix (talk) 22:05, 20 December 2014 (UTC)

I don't think you get it Fomafix. This is about adding an option to this gadget, not about automatically merging items.

See this list of items that might be merged. A lot of them are multiple items for the same taxon. Multichill (talk) 22:51, 20 December 2014 (UTC)

 Support. If (and only if) the two sitelinks to be merged lead to the same article, the redirect should be dropped automatically. Petr Matas 19:21, 21 December 2014 (UTC)

Tracked in Phabricator
Task T85347

 Oppose The only action this gadget can make is to delete it before executing the merge. It would be faster if this could be done by the API which this gadget uses. Matěj Suchánek (talk) 17:27, 26 December 2014 (UTC)

When merge new item, mark it as patrolled

I see a lot of unpatrolled redirects, I think they can be marked as patrolled when a user perform a merge with it. Sjoerd de Bruin (talk) 20:46, 11 January 2015 (UTC)

Think this not possible for this gadget. An user without patrol rights cannot patrol a change. --Fomafix (talk) 07:22, 12 January 2015 (UTC)

All confirmed and autoconfirmed users, i.e. those, who have been active here for a while, have the right. There is no technical obstacle to implementing it. Petr Matas 23:12, 12 January 2015 (UTC)

Error merging Q5505758 and Q3088400

Error while "Fusionner avec : Q3088400": http

--Vincent Simar (talk) 20:46, 13 January 2015 (UTC)

Is that the full error message? ·addshore· ^{talk to me!} 20:48, 13 January 2015 (UTC)

Looking at both histories you see to have been able to merge it? ·addshore· ^{talk to me!} 20:49, 13 January 2015 (UTC)

Error while "Creating redirect...": http

source:Q13163361 destination:Q7058862 --Wc1118 (talk) 16:00, 16 February 2015 (UTC)

I just went back and tried the same merge and it went through fine. I guess this was a one off issue! ·addshore· ^{talk to me!} 15:46, 17 February 2015 (UTC)

Automatically cut direct wikidata URL

• When you need to merge items, you have to copy wikidata URL and cut it to entity identifier. This is a little bit annoying in case you have a lot of merge pairs (like https://tools.wmflabs.org/yichengtry/checkbylist.php)
• It seems it would be useful if user could just copy wikidata URL into field "Merge with:" and gadget automatically cut URL from "https://www.wikidata.org/wiki/Q12292655" to "Q12292655". --Movses (talk) 18:50, 4 March 2015 (UTC)

If you are using yichengtry, you don't have to merge the items. Just click the yes or no button and my bot will merge the items as soons as another user confirms the edit. --Pasleim (talk) 09:31, 5 March 2015 (UTC)

Cool feature, but I talk about confortable using of Gadget-Merge.js, not about "yichengtry". It was just example for illustration. --Movses (talk) 22:25, 5 March 2015 (UTC)

I support this proposal. Maybe it's necessary to create an phab ticket for this? --XXN, 23:50, 18 December 2015 (UTC)

phab:T122019. --XXN, 09:56, 8 April 2016 (UTC)

Fix links in error message

(Note to myself)

Currently the link in the merge error message points to pages link \\Q5///. --- Jura 11:09, 12 April 2015 (UTC)

Message redirection not done

Merging Q19753321 into Q3123129 done, but it came the message "redirection not processed". Maybe because "The database has been automatically locked while the slave database servers catch up to the master" ? Jordi Roqué (talk) 08:10, 21 April 2015 (UTC)

Fusion avortée

Visiblement la fusion entre Q3725715 et Q16552187 consacré pourtant à la même personne(Enrico D'Ovidio) a bloqué. Comme c'est la première fois que je fais ce type de rapport (mes autres fusions ont fonctionné), je ne sais pas ce qu'il faut fournir pour aider... Bon courage !--Cbyd (talk) 21:43, 21 April 2015 (UTC)

J'ai enlevé le liens it:Enrico d'Ovidio et après fusionné Q16552187 avec Q3725715. --Pasleim (talk) 21:55, 21 April 2015 (UTC)

Error merging Q2995073 into Q15644410

Hi, just tried to merge Constitution of Haiti (1987) (Q2995073) into Constitution of Haiti (1987) (Q15644410) and got an error, which asked me to report the problem here. Thanks, --S.K. (talk) 20:19, 9 May 2015 (UTC)

Done, S.K.. --Succu (talk) 20:28, 9 May 2015 (UTC)

Update Arabic (ar) translation

{{Edit request}}

Please update the Arabic (ar) translation on line 47:

        lowestQid: 'دائما ادمج إلى المادة الأقدم (لا تعلم للدمج مع مادة "ادمج مع")',

--Meno25 (talk) 11:36, 8 July 2015 (UTC)

 Done (diff). Please test. --Fomafix (talk) 11:54, 8 July 2015 (UTC)

Merge Q3427203 and Q3427203

I try to merge both objects but it tells me I should report here. Thy for fixing.--Sanandros (talk) 08:02, 3 September 2015 (UTC)

Sry fixed it on my own.--Sanandros (talk) 08:04, 3 September 2015 (UTC)

 Sanandros (talk) 08:04, 3 September 2015 (UTC)

Feature suggestion: advanced mode with merge tagging at Wikipedia?

While working through Wikidata:Database reports/identical birth and death dates/1, I came across several articles that needed merging at Wikipedia.

Steps are:

• check both articles at Wikipedia
• add {{Merge|<title of other article>}} to both articles at Wikipedia. A redirect exists (or was created) at all Wikipedias (exception: lbwiki - there is no merge template).
• At Wikidata, one of the to two items would need the addition of instance of (P31) = Wikimedia duplicated page (Q17362920) and qualifier "of" (other item) (sample).
• Possibly, move all other statements to the other item.

A list of items that went through this (or should have) is at Wikidata:Database_reports/identical_birth_and_death_dates#Sitelink_conflicts, marked to merge. --- Jura 06:49, 21 September 2015 (UTC)

Not all Wikipedia's have the same templates. Also, this seems very complicated to do. Sjoerd de Bruin (talk) 06:56, 21 September 2015 (UTC)

It's just text insertion at the beginning of the article. I managed to do it even in (RTL) Arabic .. --- Jura 07:01, 21 September 2015 (UTC)

Feature suggestion: move statements to one item for duplicates

Item pairs like Mariana Griswold Van Rensselaer (Q6762024) and Mariana Griswold Van Rensselaer (Q6762043) seem to wait forever for the relevant Wikipedia to merge them (December 2014 for the sample).

To avoid that we maintain duplicate items:

• Mariana Griswold Van Rensselaer (Q6762043) should be marked with instance of (P31) = Wikimedia duplicated page (Q17362920) with qualifier of (P642) = Mariana Griswold Van Rensselaer (Q6762024)
• and all other statements and sitelinks (except the conflicting sitelink) should be moved to Mariana Griswold Van Rensselaer (Q6762024)

An option on the merge script could help do that. --- Jura 10:01, 24 September 2015 (UTC)

To do this currently with the script:

1. delete conflicting sitelink
2. merge items (redirects it)
3. restore blank version (prior to redirect)
4. re-add sitelink
5. add "Wikimedia duplicated item" "of.."

Sample at Q7347895. --- Jura 08:32, 8 October 2015 (UTC)

Make loadingMergeDestination optional

Please make loadingMergeDestination optional. I don't want to load everytime MergeDestination item. --XXN, 11:46, 3 October 2015 (UTC)

 Resolved by RicordiSamoa. --XXN, 09:42, 8 April 2016 (UTC)

Improve Italian translation

{{Edit request}}

     it: {
       conflictMessage: 'Rilevato un conflitto in ',
       conflictWithMessage: 'con',
       createRedirect: 'Crea un redirect',
       creatingRedirect: 'Creazione del redirect...',
       errorWhile: 'Errore durante "$1":',
       invalidInput: 'Attualmente solo Qid è un input valido',
       loadingMergeDestination: 'Caricamento della destinazione...',
       lowestQid: 'Unisci sempre nell'elemento più vecchio (deselezione per unire nell\'elemento "Unisci con")',
       merge: 'Unione',
       mergePendingNotification: 'Merge.js è stato avviato.<br/>Adesso vai sulla pagina dell\'altro elemento.',
       mergeProcess: 'Effettua l\'unione adesso',
       mergeSummary: 'Aggiungi il seguente testo all\'oggetto della modifica auto-generato:',
       mergeThisItem: 'Unisci questo elemento',
       mergeWithInput: 'Unisci con:',
       mergeWithProgress: 'Unione con l\'elemento...',
       mergeWizard: 'Unione guidata',
       pleaseWait: 'Attendi...',
       postpone: 'Rimanda a dopo',
       postponeTitle: 'Memorizza l\'ID di questo elemento e rimanda a dopo l\'unione',
       reportError: 'Riporta l'errore sopra [[qui]] con l\'elemento di origine e destinazione dell\'unione.',
       selectForMerging: 'Seleziona per l\'unione',
       selectForMergingTitle: 'Ricorda questo elemento come il secondo dei due elementi da unire',
       unwatchOption: 'Rimuovi gli elementi uniti dagli osservati speciali (se presenti)',
       unwatching: 'Rimozione dagli osservati speciali...'
     },

Replace italian translation with the above code. Thanks! --β₁₆ - (talk) 09:32, 6 October 2015 (UTC)

done --Pasleim (talk) 09:38, 6 October 2015 (UTC)

Sorry, I thought you copy the wiki code. There are elements <br/> and [[...]] in the code. Now I escaped them. --β₁₆ - (talk) 09:52, 6 October 2015 (UTC)

Sorry, I fixed it. --Pasleim (talk) 11:09, 6 October 2015 (UTC)

Improve Brazilian Portuguese translation

{{Edit request}}

      'pt-br': {
        conflictMessage: 'Um conflito detectado em ',
        conflictWithMessage: 'com',
        createRedirect: 'Criar um redirecionamento',
        creatingRedirect: 'Criando um redirecionamento...',
        errorWhile: 'Erro enquanto "$1":',
        invalidInput: 'Atualmente somente Qid é uma entrada válida',
        loadingMergeDestination: 'Carregando o destino da fusão...',
        lowestQid: 'Sempre faça a fusão no item mais antigo (desmarque para fundir no item "Fundir com")',
        merge: 'Fundir',
        mergePendingNotification: 'Merge.js foi iniciado.<br/>Agora você pode focar o seu navegador no outro item.',
        mergeProcess: 'Processar a fusão agora',
        mergeSummary: 'Acrescentar o seguinte texto ao sumário de edição gerado automaticamente:',
        mergeThisItem: 'Fundir este item',
        mergeWithInput: 'Fundir com:',
        mergeWithProgress: 'Fundir com...',
        mergeWizard: 'Assistente de fusões',
        pleaseWait: 'Por favor espere...',
        postpone: 'Adiar',
        postponeTitle: 'Armazenar o identificador deste item e adiar a fusão',
        reportError: 'Favor reportar sobre o erro [[aqui]] com fonte e destinação da fusão.',
        selectForMerging: 'Selecionar para fusão',
        selectForMergingTitle: 'Memorizar esse item como o segundo de dois itens a serem fundidos',
        unwatchOption: 'Remover item fundido de sua lista de páginas vigiadas (se estiver vigiando)',
        unwatching: 'Removendo da lista de páginas vigiadas...'
      },

Please replace Brazilian Portuguese translation with the above code. Thanks! --Almondega (talk) 18:01, 17 October 2015 (UTC)

 Done Matěj Suchánek (talk) 18:07, 17 October 2015 (UTC)

Thank you, please update the lowestQid message:

 lowestQid: 'Sempre faça a fusão no item mais antigo (desmarque para fundir no item "Fundir com")',

--Almondega (talk) 18:14, 17 October 2015 (UTC)

 Done No problem. Matěj Suchánek (talk) 18:41, 17 October 2015 (UTC)

failed-save

Tracked in Phabricator
Task T115892

When I tried to merge Stepanović (Q15054095) and Stepanović (Q16883834), I had this error:

Erreur durant "Fusionner avec : Q15054095" : failed-save

Envlh (talk) 16:54, 19 October 2015 (UTC)

Same problem with Gilbert de l'Aigle (Q18606660) and Gilbert de l'Aigle (Q18816762). — Ayack (talk) 17:03, 19 October 2015 (UTC)

source: cinquasia red (Q17627956); destination: cinquasia red (Q418071) --Almondega (talk) 17:11, 19 October 2015 (UTC)

Looks like a bug in the script, not specific to items. Reported on Phabricator in the Wikidata-Gadgets project. Sjoerd de Bruin (talk) 17:27, 19 October 2015 (UTC)

error during merge of Q5454663 and Q3290431 Ske (talk)

Merging of Q12348652 with Q18977419 doesn't work?

Hallo. I just tried to merge Q12348652 with Q18977419, but I received a stupid error message

Error while "Zusammenlegen mit: Q12348652": permissiondenied
Please report above error here with source and destination of merge.

that wasn't located into German. Why you changed from a working tool to an not working one? --Tlustulimu (talk) 12:51, 20 October 2015 (UTC)

You don't see the sitenotice? Matěj Suchánek (talk) 13:05, 20 October 2015 (UTC)

I dint see a sitenotice. Why the tool is inactive now? --Tlustulimu (talk) 13:20, 20 October 2015 (UTC)

Software bug, hopefully fixed soon (isn't this stated there as well?). Matěj Suchánek (talk) 13:32, 20 October 2015 (UTC)

I added some German messages to the gadget. (diff) --Fomafix (talk) 13:42, 20 October 2015 (UTC)

… and show the error message instead of the error code. (diff)

The German message in the error dialog is now

Fehler während „Zusammenlegen mit: Q12345678“: You do not have the permissions needed to carry out this action (Du hast nicht die erforderlichen Benutzerrechte für diese Aktion.)

Bitte melde diesen Fehler hier mit Quelle und Ziel der Zusammenlegung.

--Fomafix (talk) 14:50, 20 October 2015 (UTC)

Fomafix Thank you. / Danke schön. :-) --Tlustulimu (talk) 15:11, 20 October 2015 (UTC)

Feature request: Block merges of items with P460/P1889 pointing to each other

Can we add a block for such merges? If the items are to be merged, the properties need to be removed anyways. In general, such items shouldn't be merged anyways. --- Jura 13:11, 5 November 2015 (UTC)

 Resolved Thanks! --- Jura 22:25, 17 December 2015 (UTC)

Q2006176 fletting med Q568605

Disse to siden burde vært flettet, men noe står i veien for det,som jeg ikke forstår.--Trygve W Nodeland (talk) 22:21, 17 December 2015 (UTC)

OK, english: these pages should be merged, but something makes it not possible.--Trygve W Nodeland (talk) 22:22, 17 December 2015 (UTC)

It's not possible because they link to each other. This is good as one is a list of ministers, the other an item about the position. --- Jura 22:25, 17 December 2015 (UTC)

Issue with "Always merge into the older item"

I recently merged poetry collection (Q2150386) and poetry collection (Q12308638). To me it seems that the youngest item is selected rather than the oldest. Why? My "Always merge into the older item" is checked. — Finn Årup Nielsen (fnielsen) (talk) 20:57, 20 December 2015 (UTC)

Mobile phone

This discussion on the Hungarian WP says it is a pity this gadget, one of the most useful functions on WD, cannot be used on a mobile phone. I just wanted to mention this opinion as a suggestion, I did not try it. Oliv0 (talk) 07:02, 27 December 2015 (UTC)

You saying "one of the most useful functions on WD"makes me feel like this should be a built in feature ;) ·addshore· ^{talk to me!} 09:57, 26 January 2016 (UTC)

merge Q20786996 with Q333877

Cant't merge because of property P1672. It's the same plant. --Nordelch (talk) 12:21, 23 January 2016 (UTC)

Nordelch (talk): This not a problem with Gadget-Merge.js. It is intended that one should not merge two items that are linked (this restriction has recently been implemented in the Wikidata software). Whether it should be merged is open for discussion: One item is for the plant, the other item is (apparently) for the nut. I do not think they should be merged. Look at apple (Q89) and Malus pumila (Q158657). There the fruit and the tree is separated. natural product of taxon (P1582) makes no sense if fruits and plants are merged. On a different note: the Swedish link could be move to the other item. — Finn Årup Nielsen (fnielsen) (talk) 15:05, 24 January 2016 (UTC)

Die Objekte Q16428906 und Q215780 behandeln beide den semitischen Vornamen Thomas. Ich kann die Fehlermeldung (property P460) nicht deuten. Aarp65 (talk) 19:42, 6 February 2016 (UTC)

Ukrainian translation

{{Edit request}}

uk: {
        conflictMessage: 'Виявлено конфлікт у ',
        conflictWithMessage: 'з',
        createRedirect: 'Створити перенаправлення',
        creatingRedirect: 'Створення перенаправлення...',
        errorWhile: 'Помилка при «$1»:',
        invalidInput: 'Наразі лише ідентифікатор (Qid) може бути валідними вхідними даними',
        loadingMergeDestination: 'Завантаження цільової сторінки до об\'єднання...',
        lowestQid: 'Завжди приєднувати до старішого елемента (зніміть позначку, щоб приєднати до елемента, вказаного в «Об\'єднати з»)',
        merge: 'Об\'єднати',
        mergePendingNotification: 'Merge.js було запущено.<br/>Тепер Ви можете перемкнути свій браузер на інший елемент.',
        mergeProcess: 'Виконати об\'єднання зараз же',
        mergeSummary: 'Додати цей текст до автоматичного опису редагування:',
        mergeThisItem: 'Приєднати цей елемент',
        mergeWithInput: 'Об\'єднати з:',
        mergeWithProgress: 'Об\'єднати з...',
        mergeWizard: 'Майстер об\'єднання',
        pleaseWait: 'Зачекайте, будь ласка...',
        postpone: 'Відкласти',
        postponeTitle: 'Збережіть ідентифікатор цього елемента та відкладіть об\'єднання на пізніше',
        reportError: 'Будь ласка, повідомте про помилку [[отут]], вказавши вихідний та цільовий елементи до об\'єднання.',
        selectForMerging: 'Вибрати для об\'єднання',
        selectForMergingTitle: 'Запам\'ятати цей елемент як другий з тих, котрі треба об\'єднати',
        unwatchOption: 'Вилучити приєднаний елемент з Вашого списку спостереження (якщо він був у ньому)',
        unwatching: 'Вилучення зі списку спостереження...'
      },

Please, add Ukrainian translation--Piramidion (talk) 15:52, 5 March 2016 (UTC)

 Done Matěj Suchánek (talk) 16:37, 5 March 2016 (UTC)

Close/Cancel

It's necessary to repair "Cancel" button or to add a new button (X) for closing Merge.js pop-up. Currently if merge operation failed, "Cancel" button (plus everything in this tab) become inactive and the only option(s) you have is to reload or close current tab in browser. You can test this on any pair of items with conflicting sitelinks. --XXN, 09:59, 8 April 2016 (UTC)

I just noticed this too. You can close it by pressing escape on the keyboard, but there's no way of doing it with the mouse or a touchscreen as far as I can tell. - Nikki (talk) 13:27, 18 April 2016 (UTC)

@XXN, Nikki:  Fixed --Ricordisamoa 13:01, 8 May 2016 (UTC)

Request: Improvements for keyboard navigation

This new merge gadget is a bit more keyboard-friendly (it's actually possible to tab to the submit button!), but there's still two things I'd really like to see:

When the merge dialog opens, it seems nothing is focused. It would be better if the "Merge with" field were focused (didn't it used to be?). Right now I have to tab to "Cancel" (pressing escape cancels anyway), then "Merge" (which I obviously don't need until after I reach the "Merge with" field), then again to the "Merge with" field.

Tabbing from the "Merge with" field to the "Merge" button is 8 tabs which is not very efficient. Pressing the enter key normally submits a form and it would be nice if pressing the enter key would submit the merge form too.

- Nikki (talk) 17:17, 10 April 2016 (UTC)

+1 for focus on "Merge with" when the UI is loaded. --ValterVB (talk) 17:45, 10 April 2016 (UTC)

+1 for the initial focus issue. -- LaddΩ chat ;) 21:25, 14 April 2016 (UTC)

@Nikki, ValterVB, Laddo:  Done focus on "Merge with" field. Just like with every OOjs UI dialog (phab:T125860) the primary action (i.e. "Merge") can be triggered via Ctrl+Enter. --Ricordisamoa 13:37, 8 May 2016 (UTC)

@Ricordisamoa: Thanks for fixing the focus issue :) I would still like enter to submit it though, because that's how everything else I can think of that I've used (including Wikidata's own editing fields) has worked for as long as I can remember. I don't stop to consider whether something behaves normally or not before deciding what to press, I just instinctively press enter to submit. Doing nothing when I press enter makes it feel broken. :/ - Nikki (talk) 17:48, 8 May 2016 (UTC)

Error while merge

Cannot merge: Q21504556 → Q573634

---

Error while "Merge with: Q573634": Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P1889)

Please report above error here with source and destination of merge.

---

Ping me back. Cheers! {{u|Checkingfax}} {Talk} 08:00, 12 April 2016 (UTC)

@Checkingfax: This was blocked by the software because both items are interlinked by different from (P1889), thus they should not be merged. Matěj Suchánek (talk) 12:29, 12 April 2016 (UTC)

Hi, Matěj Suchánek. Thank your for your reply. I already stated that in my inquiry above. Can you please elaborate on my existing statement? Your reply just puts the words in a different order. Ping me back. Cheers! {{u|Checkingfax}} {Talk} 17:58, 12 April 2016 (UTC)

@Checkingfax: What specifically do you want to know? You already know why it was blocked. In fact, this report wasn't neccessary because it isn't an error in the gadget but that's not your fault. Matěj Suchánek (talk) 18:15, 12 April 2016 (UTC)

Hi, Matěj Suchánek. I tried to merge "Torres" with "Torres", both described as family/surnames.

The error thrown said to report it here. That is what I have done. Now I would like to know what makes Torres the same as Torres. Both of your replies, although I very much appreciate them, have been non-responsive. Ping me back. Cheers! {{u|Checkingfax}} {Talk} 18:22, 12 April 2016 (UTC)

@Checkingfax: Could be because a Wikimedia disambiguation page (Q4167410) is not the same thing as a family name (Q101352)? Matěj Suchánek (talk) 18:25, 12 April 2016 (UTC)

I cleaned them up. Sitelinks and descriptions got mixed-up. As ukwiki has two disambiguation items for "Torres", we end up with two items. Family name is at Q21504556.
--- Jura 18:37, 12 April 2016 (UTC)

Hi, Jura1 and Matěj Suchánek. Thank you. This whole mess started because the two Torres lacked a description, which I added, but now Torres (Q573634) again lacks a description. Ping me back. I love to learn. Tell why you are doing what instead of just doing it or dismissing it. When items lack a description it makes it hard to pick the right one from the item menu. Cheers! {{u|Checkingfax}} {Talk} 18:57, 12 April 2016 (UTC)

Merge failed re property P1889

Seeking to merge 2 items about the human name "Mariam": Q18082274 to Q16275425.

"Error while "Merge with: Q16275425": Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P1889)

Please report above error here with source and destination of merge."

I removed the "different from" data on each page, and completed the move. Fayenatic london (talk) 13:06, 19 April 2016 (UTC)

• We should improve the error message: (1) It's not really an error, the items just shouldn't be merged; (2) no need to report this here. If the two items link to each other, almost always they shouldn't be merged.
  --- Jura 13:16, 19 April 2016 (UTC)

Error with P178

Hi

i've try to merge Q23894238 with Q2618907

and i've the "Erreur during "merge with : Q2618907" : Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P178)" the error warning said that i'must write there :)

P178 are for developer, but normaly there are no problem. P178 is on Q23894238, not on Q2618907  – The preceding unsigned comment was added by Dj- (talk • contribs) at 20:28, 20 mag 2016‎ (UTC).

Aptana Inc. (Q2618907) is the software house, Aptana Studio (Q23894238) is the software, are different things. --ValterVB (talk) 06:45, 21 May 2016 (UTC)

Merge Q6236303 and Q19064697

Please merge the two items above, they link to the same person. --Giorgio Michele (talk) 22:04, 21 May 2016 (UTC)

 Moved the German link,  Not done the merge as John Grey, 1st Earl of Tankerville (Q6236303) is for the person and Grey, John (Q19064697) is a biographical article (Q19389637) about them. Matěj Suchánek (talk) 11:53, 22 May 2016 (UTC)

Thanks, I think it's ok. --Giorgio Michele (talk) 12:45, 22 May 2016 (UTC)

error merging

Error while "Merge with: Q890528" with Q22026039: Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P361) --Dodi123 (talk) 19:57, 30 May 2016 (UTC)

Like the message says, you're not allowed to merge things which are linked to each other. When things are linked to each other, it either means there is actually a difference between them, or there's an incorrect statement which needs fixing. In this case, there is a difference so they should not be merged. Shenzhen Open (Q22026039) is for pages which cover both Shenzhen Open (WTA) (Q890528) (a women's tennis tournament) and ATP Shenzhen Open (Q15781252) (a men's tennis tournament). - Nikki (talk) 06:57, 31 May 2016 (UTC)

Thank you. It's correct. --Dodi123 (talk) 15:48, 31 May 2016 (UTC)

Merge failed

Trying to merge Q206701 into Q20754771 MPF (talk) 12:46, 16 June 2016 (UTC)

merge Q14706104 into Q4960100

Trying to merge Q14706104 into Q4960100.

Error while "Merge with: Q4960100": You must provide unique ids Stephen G. Brown (talk) 21:33, 23 June 2016 (UTC)

@Stephen G. Brown: That error means the ID you entered is the same as the current item's ID. It's possible that there's a bug somewhere but it usually just means you accidentally mixed up the IDs (it's easily done, it happens to me from time to time :)). I've merged these two items now. If you get the same error in the future, check that you haven't mixed up the IDs and if you still can't get it to work, let us know. :) - Nikki (talk) 22:46, 23 June 2016 (UTC)

What are the IDs? Do you mean Q14706104 and Q4960100? I went to the more recent page (Q14706104), clicked on "merge with", typed Q4960100 (the older page) into the top box, unticked the first checkbox (Always merge into the older item, since it says to untick it), and pressed "Merge". Stephen G. Brown (talk) 23:17, 23 June 2016 (UTC)

Error 2

I got an error:

Error while "Merge with: Q1272741": Attempted modification of the item failed. (The statement has already a reference with hash 37e63a2f034068f3a47e4708046fbd32619e04f4)

Please report above error here with source and destination of merge.

When trying to merge Q25712356 with Q1272741.  – The preceding unsigned comment was added by ChristianKl (talk • contribs) at 21:44, 9 lug 2016‎ (UTC).

Strange message, since the hash 37e63a2f034068f3a47e4708046fbd32619e04f4 actually is only present at Q25712356 and not at Q1272741. This can be checked using the API: /w/api.php?action=wbgetclaims&format=json&entity=Q1272741&property=P31 & /w/api.php?action=wbgetclaims&format=json&entity=Q25712356&property=P31. Mbch331 (talk) 17:55, 10 July 2016 (UTC)

The problem isn't the gadget, but the API. It's the Wikidata API that generates the error. Mbch331 (talk) 17:58, 10 July 2016 (UTC)

This is odd, and the first time I have heard of it happening, but it will be hard to investigate as the state of the data has already moved on (the items are merged). Be sure to post again at Wikidata:Contact_the_development_team if this happens again! ·addshore· ^{talk to me!} 18:22, 13 July 2016 (UTC)

Macedonian (mk) version

{{Editprotected}} Hello admins. Could someone add this Macedonian version to the page? Thanks a lot. --B. Jankuloski (talk) 19:22, 18 July 2016 (UTC)

mk: {
        conflictMessage: 'Утврдена спротиставеност во ',
        conflictWithMessage: 'со',
        createRedirect: 'Направи пренасочување',
        creatingRedirect: 'Правам пренасочување...',
        errorWhile: 'Грешка при „$1“:',
        invalidInput: 'Во мигов може да се внесе само Qid',
        loadMergeDestination: 'Вчитај ја целната страница при успешно спојување',
        loadingMergeDestination: 'Ја вчитувам целната страница на спојувањето...',
        lowestQid: 'Секогаш спојувај во постариотпредмет (отштиклирајте за да споите во предметот „Спој со“)',
        merge: 'Спој',
        mergePendingNotification: 'Merge.js е започнат.<br/>Сега можете да го отворите другиот предмет.',
        mergeProcess: 'Спроведи го спојувањето сега',
        mergeSummary: 'Придодај го следниов текст кон самосоздадениот опис на дејството:',
        mergeThisItem: 'Спој го предметов',
        mergeWithInput: 'Спој со:',
        mergeWithProgress: 'Спој со...',
        mergeWizard: 'Спојувач',
        pleaseWait: 'Почекајте...',
        postpone: 'Одложи',
        postponeTitle: 'Зачувај ги предметните назнаки и одложи го спојувањето',
        reportError: 'Пријавете ја грешката [[тука]] со изворната и целната страница на спојувањето.',
        selectForMerging: 'Избери за спојување',
        selectForMergingTitle: 'Запомни го предметов како втор од двата што се спојуваат',
        unwatchOption: 'Отстрани ја споената страница од набљудуваните (ако е таму)',
        unwatching: 'Отстранувам од набљудуваните...'
      },

 Done - Mbch331 (talk) 19:30, 18 July 2016 (UTC)

Auke

Please merge Q16274719 with Q771150. Both are about the Frisian masculine given name Auke, but when I tried to merge them, an error occurred with the following message: "Error while "Merge with: Q771150": Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P1889). Please report above error here with source and destination of merge." Ieneach fan 'e Esk (talk) 14:56, 25 July 2016 (UTC)

Auke (Q16274719) contained statements that aren't valid anymore. I'm going to move the sitelink by hand and delete this item. Sjoerd de Bruin (talk) 15:18, 25 July 2016 (UTC)

Apparently there was also Auke (Q771167), merged the first item to that (without the said sitelink of course). Sjoerd de Bruin (talk) 15:19, 25 July 2016 (UTC)

Q8083449 and Q1181337 not merged, why?

Q8083449 and Q1181337 not merged, why?--Хомелка (talk) 09:48, 29 July 2016 (UTC)

They link to each (with the wrong property). They shouldn't be merged as one is a disambiguation page, the other an item about the name.
--- Jura 09:56, 29 July 2016 (UTC)

Constantijn Huygens (Q560746)

aim:Constantijn Huygens (Q560746) from Q21596649 Fehler während „Zusammenlegen mit: Q560746“: Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P910) Bitte melde diesen Fehler hier mit Quelle und Ziel der Zusammenlegung. even after deletion --Oursana (talk) 22:37, 12 August 2016 (UTC)

Why are you trying to merge a former category item in a item about a person? Sjoerd de Bruin (talk) 22:42, 12 August 2016 (UTC)

Removed the unmotivated deletions on Q21596649, articles and categories should be seperated. Sjoerd de Bruin (talk) 22:43, 12 August 2016 (UTC)

since when do they have to be separated when there is no gallery. Then linking from commons to the wp-articles is missing

see Wikidata talk:Wikimedia Commons#Are we there yet? guidance on linking--Oursana (talk) 22:52, 12 August 2016 (UTC)

Merge request

Merge Q21090684 into Q228009, please  – The preceding unsigned comment was added by MPF (talk • contribs) at 12. 9. 2016, 08:04 (UTC).

 Not done Interlinked using original combination (P1403), apparently different concepts which should have an item each. Matěj Suchánek (talk) 12:51, 12 September 2016 (UTC)

Merge request

Please, merge Q18396756 into Q6310832. Thanks.--Alfredalva (talk) 21:40, 2 October 2016 (UTC)

 Done Matěj Suchánek (talk) 18:30, 23 December 2016 (UTC)

Merge problem

I attempted to merge Mechthild (Q1796474) and Mechthild (Q20999977), but it didnt work and replied "The two items cannot be merged because one of them links to the other using property P1889". I don't have much experience with this, so I hope someone can merge them. Thanks--Concus Cretus (talk) 03:44, 18 October 2016 (UTC)

The first is an item about given name, the second is a disambiguation, they are different item. --ValterVB (talk) 06:30, 18 October 2016 (UTC)

That is an error. They both describe the name and a disambiguation page for the name. There are no overlapping articles on any Wikipedias.--Concus Cretus (talk) 09:19, 18 October 2016 (UTC)

I moved the enwiki sitelink. --Succu (talk) 09:29, 18 October 2016 (UTC)

@Succu Thanks! I moved the last remaining article (Italian Wikipedia) so Q20999977 is now empty. Hope someone can merge it.--Concus Cretus (talk) 13:25, 18 October 2016 (UTC)

itwiki is a real disambiguation page. I moved the sitelink back. Ws have to retain both items. --Succu (talk) 13:30, 18 October 2016 (UTC)

I added the content to the itwiki so it covers the Germanic name "Mechthilde" now. Now it is the same like other wikis on Q1796474.--Concus Cretus (talk) 13:53, 18 October 2016 (UTC)

Following the rules of it.wiki, you have done an error. On it.wiki, like on en.wiki, disambiguation pages are pages that list word with the same spelling but that can have different meaning, in fact on it.wiki page you can found an asteroid, and if tomorrow a book titled "Mechthild" will win a literary award, on it.wiki we can add without problem the book to the disambiguation, because this is the concept of disambiguation. If the page must list only people with the same name or with the same surname isn't a disambiguation. You can read WikiProject Disambiguation pages where is explained what is a disambiguation and that we don't mix item. I restore the previous situation. --ValterVB (talk) 18:02, 18 October 2016 (UTC)

Galician translation update

{{Editprotected}} Please update the Galician localization with the following strings:

      gl: {
        conflictMessage: 'Detectouse un conflito en ',
        conflictWithMessage: 'con',
        createRedirect: 'Crear unha redirección',
        creatingRedirect: 'Creando a redirección...',
        errorWhile: 'Produciuse un erro ao "$1":',
        invalidInput: 'Actualmente, as únicas entradas válidas son os identificadores Q dos elementos',
        loadMergeDestination: 'Cargar o destino da fusión ao rematar',
        loadingMergeDestination: 'Cargando o destino da fusión...',
        lowestQid: 'Fusionar sempre no elemento máis vello (desmarca a opción para fusionar no elemento do campo "Fusionar con")',
        merge: 'Fusionar',
        mergePendingNotification: 'Merge.js iniciouse.<br/>Xa podes ir co navegador ao outro elemento.',
        mergeProcess: 'Proceder agora á fusión',
        mergeSummary: 'Engadir o seguinte texto ao resumo de edición automático:',
        mergeThisItem: 'Fusionar este elemento',
        mergeWithInput: 'Fusionar con:',
        mergeWithProgress: 'Fusionar con...',
        mergeWizard: 'Ferramenta de fusións',
        pleaseWait: 'Por favor, espera...',
        postpone: 'Pospoñer',
        postponeTitle: 'Gardar o identificador deste elemento e pospor a fusión',
        reportError: 'Informa do erro anterior [[aquí]] coa orixe e mais o destino da fusión.',
        selectForMerging: 'Seleccionar para a súa fusión',
        selectForMergingTitle: 'Lembrar este elemento como o segundo dos dous a fusionar',
        unwatchOption: 'Eliminar o elemento fusionado da túa lista de vixilancia (se está nela)',
        unwatching: 'Eliminando da lista de vixilancia...'
      },

Thank you! --Toliño (talk) 11:01, 27 October 2016 (UTC)

 Done (diff) --Fomafix (talk) 11:24, 27 October 2016 (UTC)

Bitburg

I tried to merge dewiki:Bitburg (Q258974) with the wikimedia:Bitburg (Q8909788), but it failed. Please help! --Bungert55 (talk) 14:34, 2 November 2016 (UTC)

The first one is a municipality while the other is a Wikimedia category, different concepts. Removal of valid sitelinks count as vandalism, though. Sjoerd de Bruin (talk) 14:44, 2 November 2016 (UTC)

This comment is not very helpful. Of course the first is a municipality, but the second is the corresponding Wikimedia category, thus the two should be merged, like all other corresponding data objects. The link to the dewiki-Kategorie is misleading. I deleted it in preparation of the unsuccessful merger. You say that counts as vandalism - how else can a merger be prepared? --Bungert55 (talk) 15:11, 2 November 2016 (UTC)

Please point me to "all other corresponding data objects" and explain why the German sitelink is "misleading". Sjoerd de Bruin (talk) 15:15, 2 November 2016 (UTC)

merge unsuccessful

When trying to merge Q1213827 with Q1537946, i got the following error message with a cryptic reference to property P1889, which shud have a link explaining what that property is and how to fix/remove it: "Error while "Merge with: Q1537946": Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P1889)"

The descriptions of item Q1213827 are incorrect in all the three languages provided, and the item shud therefore disappear and be merged into Q1537946, which has the correct description. --Espoo (talk) 09:43, 11 November 2016 (UTC)

I moved some sitelinks. Now Kenneth (Q1213827) contains only links to disambiguation pages. --Pasleim (talk) 09:52, 11 November 2016 (UTC)

Greek (el)

Pls add the Greek phrase for 'Always merge into the older item (uncheck to merge into the "Συγχώνευση με" item)', 'Πάντα να γίνεται συγχώνευση στο παλαιότερο αντικείμενο (καταργήστε την επιλογή για να συγχωνευθεί με το αντικείμενο "Συγχώνευση με")',

Also, where can I give the translations of: Select for merging (Επιλέξτε για συγχώνευση)

Remember this item as the second one of the two items to be merged (Να θυμάσαι αυτό το αντικείμενο σαν το δεύτερο από τα δύο αντικείμενο που θα συγχωνευθούν)

Xaris333 (talk) 22:23, 13 November 2016 (UTC)

 Done Matěj Suchánek (talk) 13:32, 14 November 2016 (UTC)

Correction in line of mk version

{{Editprotected}} Hello. I will be thankful if someone can correct the lowestQid in the mk version, to read as follows. Cheers. --B. Jankuloski (talk) 09:16, 25 November 2016 (UTC)

lowestQid: 'Секогаш припојувај кон постариот предмет (отштиклирајте за да припоите во предметот „Спој со“)',

 Done Matěj Suchánek (talk) 12:19, 25 November 2016 (UTC)

Property P527

Seeking to merge two items on the same topic, items Q528163 and Q25648673, both regarding CasaPound Italia, and received an error that merge was not possible because one links to the other with property P527. Giovanni.iaboni99 (talk) 20:37, 14 December 2016 (UTC)

Rank gets lost?

I merged Portrait of Saskia (Q27036626) into Portrait of Saskia (Q21969088), both items had creator (P170) -> Rembrandt (Q5598), first with rank deprecated, second one with normal rank. After the merge only the deprecated one was still there. In this case this was correct, but is this intentional or not? Multichill (talk) 17:44, 23 December 2016 (UTC)

As far as I can see, statements are compared by value and qualifiers, and if they are same, only the references are moved. So the interpretation should not be that "the deprecated one is always kept" but "the target one is always kept". Matěj Suchánek (talk) 18:02, 23 December 2016 (UTC)

Cabaret - Merge Failure

Q27976507 & Q131183 could not be merged. --Manuspanicker (talk) 11:41, 29 December 2016 (UTC)

They shouldn't me merged. Once should be about a type of tavern (Q154250) and the other one about a type of kleinkunst (Q1746926). Currently cabaret (Q131183) is a mess, because it is about both. Mbch331 (talk) 11:53, 29 December 2016 (UTC)

@User:Mbch331, then - that's it! we will leave them! Ta. --Manuspanicker (talk) 12:32, 29 December 2016 (UTC)

Brennecke Begriffsklärungsseite

Die Objekte Q909095 und Q20995901 beziehen sich beide auf die Nachnamensbegriffsklärungsseite Brennecke. Offensichtlich wird durch die Eigenschaft P1889 (verschieden von) die englischsprachige Kategorie surname als nicht vereinbar mit der deutschsprachigen Kategorie Begriffsklärung (engl.: disambiguation) angesehen. Streng genommen ist eine Seite mit Personen des gleichen Nachnamens auch keine Bergriffsklärungsseite, da nur der zweite Teil des bürgerlichen Namens, nämlich der Nachname, identisch ist und somit keine Verwechslung möglich ist. Von einer Nachnamensseite wird in der deutschen Wikipedia jedoch mehr verlangt, als lediglich eine Auflistung der enzyklopädisch relevanten Personen, sondern auch eine onomastische Untersuchung des Familiennamens.

Ich habe die beiden Objekte zusammengeführt, da alle verlinkten Wikipediaartikeln sich ausschliesslich auf den Familiennamen beziehen. --Pasleim (talk) 21:08, 8 January 2017 (UTC)

Merge

Please, merge Q16831706 and Q16867744 --YarikUkraine (talk) 19:38, 27 January 2017 (UTC)

 Not done family name has to use a different item than disambiguation page (Q27924673). Matěj Suchánek (talk) 10:16, 28 January 2017 (UTC)

Change pl translation

Please change Polish translation (pl) to this code. Sp5uhe (talk) 07:02, 6 February 2017 (UTC)

      pl: {
        conflictMessage: 'Wykryto konflikt ',
        conflictWithMessage: 'z',
        createRedirect: 'Utwórz przekierowanie',
        creatingRedirect: 'Tworzenie przekierowania...',
        loadingMergeDestination: 'Ładowanie łączonego elementu...',
        loadMergeDestination: 'Załaduj połączony element',
        lowestQid: 'Zawsze łącz ze starszym elementem',
        merge: 'Połącz',
        mergePendingNotification: 'Merge.js zostało uruchomione.<br/>Możesz teraz przejść do innego elementu.',
        mergeProcess: 'Rozpocznij proces łączenia',
        mergeThisItem: 'Połącz ten element',
        mergeWithInput: 'Połącz z elementem:',
        mergeWithProgress: 'Łączę z...',
        mergeWizard: 'Kreator łączenia',
        pleaseWait: 'Czekaj...',
        postpone: 'Odłóż na później',
        postponeTitle: 'Zapamiętaj identyfikator tego elementu i odłóż łączenie na później',
        selectForMerging: 'Zaznacz do połączenia',
        selectForMergingTitle: 'Zapamiętaj ten element jako drugi do połączenia dwóch elementów',
        unwatchOption: 'Usuń łączone elementy z mojej listy obserwowanych (jeśli na niej były)',
        unwatching: 'Usuwanie z listy obserwowanych...'
      },

 Done Matěj Suchánek (talk) 14:04, 6 February 2017 (UTC)

@Sp5uhe: Problem: tab name has progress form. --Wargo (talk) 21:13, 6 February 2017 (UTC)

Full translation:

conflictMessage: 'Wykryto konflikt ',
conflictWithMessage: 'z',
createRedirect: 'Utwórz przekierowanie',
creatingRedirect: 'Tworzenie przekierowania...',
errorWhile: 'Błąd podczas operacji „$1”:',
invalidInput: 'Poprawna forma to Qid',
loadingMergeDestination: 'Ładowanie łączonego elementu...',
loadMergeDestination: 'Załaduj połączony element',
lowestQid: 'Zawsze łącz ze starszym elementem',
merge: 'Połącz',
mergePendingNotification: 'Merge.js zostało uruchomione.<br/>Możesz teraz przejść do innego elementu.',
mergeProcess: 'Rozpocznij proces łączenia',
mergeSummary: 'Dopisz ten tekst do opisu zmian:',
mergeThisItem: 'Połącz ten element',
mergeWithInput: 'Połącz z elementem:',
mergeWithProgress: 'Łączę z...',
mergeWizard: 'Kreator łączenia',
pleaseWait: 'Czekaj...',
postpone: 'Odłóż na później',
postponeTitle: 'Zapamiętaj identyfikator tego elementu i odłóż łączenie na później',
reportError: 'Zgłoś powyższy błąd [[tutaj]] z podaniem elementu źródłowego i docelowego do połączenia.',
selectForMerging: 'Zaznacz do połączenia',
selectForMergingTitle: 'Zapamiętaj ten element jako drugi do połączenia dwóch elementów',
unwatchOption: 'Usuń łączone elementy z mojej listy obserwowanych (jeśli na niej były)',
unwatching: 'Usuwanie z listy obserwowanych...'

Merge gadget not working?

Hi. I've been trying to merge a few things using the auto merge gadget and it's not working. The gadget is checked. I've been using it since I joined Wikidata. I am using Chrome and Firefox and it's not working on either. Thanks for your help and for making a great tool. Missvain (talk) 01:54, 9 February 2017 (UTC)

{{Edit request}} As per phab:T149807 someone should add something like MergeDialog.static.name = 'mergeDialog'; before MergeDialog.static.title = messages.mergeWizard; --Ricordisamoa 09:53, 9 February 2017 (UTC)

 Done --Pasleim (talk) 10:18, 9 February 2017 (UTC)

Thank you, it works again now. --Ricordisamoa 17:50, 9 February 2017 (UTC)

Q23907719 and Q937379 can be merged

Q23907719 and Q937379 can be merged but the merge tool was not able to do so. Can someone do this please? Thank you in advance! Ymnes (talk) 17:02, 3 March 2017 (UTC)

They are different concepts. The first item is about given name + surname the second item is about given name --ValterVB (talk) 08:37, 4 March 2017 (UTC)

I'm not convinced, because on Wikipedia itself the articles are addressing exactly the same theme Florian. If there can be seen a difference between Florian and Florian, the differences has not been introduced on the Wikipedia's. Ymnes (talk) 09:32, 4 March 2017 (UTC)

As you can see, the relation between these items is expressed using part of (P361)/has part(s) (P527), ie. one is part of another. If you believe, there's a link which fits better in another item, feel free to remove and add it there. Matěj Suchánek (talk) 09:44, 4 March 2017 (UTC)

@User talk:Matěj Suchánek - As you can read in my text here above, the difference where to use which Wikipedia article is incomprehensible. I find the reader is not served in this way. Ymnes (talk) 14:29, 4 March 2017 (UTC)

It is not incomprehensible to me. It is straightforward for me to understand the difference. They should not be merge. How the different Wikipedias link to them are up to each individual Wikipedia. It depends on what the Wikipedia article is about. — Finn Årup Nielsen (fnielsen) (talk) 08:43, 5 March 2017 (UTC)

Merging of Q7675532 and Q2388294

Both objects (Q7675532 and Q2388294) list people with the surname Tahirović. Aarp65 (talk) 12:40, 23 March 2017 (UTC)

The first is an item about surname, the second is a disambiguation item, and we don't mix this kind of item, but I moved all the sitelink in the second item becasue are al disambiguation (You can find them in "Special:Disambiguation pages") --ValterVB (talk) 18:51, 23 March 2017 (UTC)

Synonyms of a species

Hi! I'd like to merge Parus nuchalis (Q2784651) into Machlolophus nuchalis (Q27075358), because they're the same species of bird. Thanks. --Kadellar (talk) 20:33, 31 March 2017 (UTC)

Try a second look, Kadellar Parus nuchalis (Q2784651) is original combination (P1403) of White-naped tit (Q27075358). --Succu (talk) 21:13, 31 March 2017 (UTC)

Error while "Creating redirect...": [WOOgFApAMCEAAD5u17cAAAAY] Database query error

Error while "Creating redirect...": [WOOgFApAMCEAAD5u17cAAAAY] Database query error. Happened while merging two entries on navigation templates for Korean language, Q14440200 into Q14336378. Reason unknown but not due to conflicting sets of Wikipedias (ar, en, ko, no, pt, tl in one of them; ru, az, ba in another).Tatewaki (talk) 13:37, 4 April 2017 (UTC)

• The gadget actually merged these entries, even though reported about an error. Tatewaki (talk) 13:39, 4 April 2017 (UTC)

@Tatewaki: I just looked into this very briefly: This is a database locking error, that can happen in some rare cases. This is the only case I could find of this same error happening in the logs (covering the last 90 days), so I think we can just ignore this for now. Should this (a database query error during merge) happen again, please let us know. Cheers, Hoo man (talk) 07:34, 6 April 2017 (UTC)

Merge error message on Q17745899

I received the following error message when trying to merge Q3314653 into Q17745899. This is the result of a taxonomic name change, cf. http://linnet.geog.ubc.ca/Atlas/Atlas.aspx?sciname=Erythranthe+alsinoides. The new name is Erythranthe alsinoides (Q17745899). --Wsiegmund (talk) 00:43, 8 April 2017 (UTC)

Error while "Merge with: Q17745899": Attempted modification of the item failed. (The two items cannot be merged because one of them links to the other using property P566)
Please report above error here with source and destination of merge.

I have this resolved, I think. --Wsiegmund (talk) 03:53, 9 April 2017 (UTC)

HR translation

{{Edit protected}} Please, add translation in Croatian:

 hr: {
        conflictMessage: 'Otkriven je sukob ',
        conflictWithMessage: 's',
        createRedirect: 'Napravi preusmjeravanje',
        creatingRedirect: 'Stvaram preusmjeravanje...',
        errorWhile: 'Pogrješka za vrijeme "$1":',
        invalidInput: 'Trenutačno se može unijeti samo Qid',
        loadMergeDestination: 'Po završetku učitaj završnu stavku',
        loadingMergeDestination: 'Učitavam završnu stavku...',
        lowestQid: 'Uvijek spoji sa starijom stavkom (odznačite ako želite spojiti sa stavkom navedenom u polju "Spoji s")',
        merge: 'Spoji',
        mergePendingNotification: 'Merge.js je pokrenut.<br>Možete nastaviti raditi na drugim stavkama.',
        mergeProcess: 'Spoji stavku sada',
        mergeSummary: 'Automatski stvorenom sažetku uređivanja dodaj sljedeći tekst :',
        mergeThisItem: 'Spoji ovu stavku',
        mergeWithInput: 'Spoji s:',
        mergeWithProgress: 'Spajam s...',
        mergeWizard: 'Čarobnjak za spajanje',
        pleaseWait: 'Molimo pričekajte...',
        postpone: 'Spoji kasnije',
        postponeTitle: 'Spremi ovu stavku i spoji kasnije',
        reportError: 'Molimo prijavite gornju pogrješku [[ovdje]] s početnom i završnom stavkom spajanja.',
        selectForMerging: 'Označi za spajanje',
        selectForMergingTitle: 'Upamti ovu stavku kao drugu od dvije za spajanje',
        unwatchOption: 'Ukloni spojenu stavku s popisa praćenja (ako je bila na njemu)',
        unwatching: 'Uklanjam s popisa praćenja...'
      }

Thanks.--MaGa 12:56, 8 April 2017 (UTC)

 Done Matěj Suchánek (talk) 14:32, 8 April 2017 (UTC)

{{Edit protected}} Please, correct:

mergeWithProgress: 'Spajam s...', 

->

mergeWithProgress: 'Spoji s...', 

Thanks.--MaGa 15:37, 8 April 2017 (UTC)

 Done Matěj Suchánek (talk) 17:35, 8 April 2017 (UTC)

fish family with only one genus

Q14721240 should merge with Q2140084. This fish family has only 1 genus. --Nordelch (talk) 17:02, 10 April 2017 (UTC)

Hi Nordelch! I moved most sitelinks to the genus item. --Succu (talk) 17:35, 10 April 2017 (UTC)

Thanks! --Nordelch (talk) 09:28, 11 April 2017 (UTC)

Merge failed ( Tokyo City (Q1207735) with special wards of Tokyo (Q308891) )

Merging https://www.wikidata.org/wiki/Q308891#sitelinks-wikipedia with https://www.wikidata.org/wiki/Q7473516 failed. Kazkaskazkasako (talk) 16:59, 20 April 2017 (UTC)

Exmoor, Exmoor National Park

I tried to merge Exmoor National Park, and Exmoor (seem to be the same); Q29511798 and Q593627), but it fails. Are there reasons not to merge them? Hobbema (talk) 01:15, 22 April 2017 (UTC)

Apparently

⟨ Exmoor (Q593627)    ⟩ located in protected area (P3018) ⟨ Exmoor National Park (Q29511798)    ⟩

. If you want to know more about this, Project chat is a better place to ask this question. But that statement I mentioned at the beginning is the reason you can't merge the items. Mbch331 (talk) 05:53, 22 April 2017 (UTC)

Error merging

I had a problem with merging Q18857 and Q12214415, it gave the following errormessage: Fout tijdens "Samenvoegen met: Q18857": Can't create redirect (possibly because redirects between this kind of entity are not supported at all). (De pagina is niet aangemaakt. Deze bestaat al.) --Q.Zanden questions? 18:46, 24 April 2017 (UTC)

I could reproduce it and reported it at Wikidata:Contact the development team#Can't create redirect. Matěj Suchánek (talk) 19:41, 24 April 2017 (UTC)