Jan 20 2018
@Phantom42, I have no environment set for this right now. Feel free to take it. I already did what I could
Jan 19 2018
@Phantom42 , would be nice to add T139456 to it
Jan 9 2018
@Phantom42 I think you could find some clues here:
Jan 8 2018
What is needed to fix it is just to find part of Translate Extension which broke after upgrading jQuery and fix it. That's all.
And that part will be Translate\resources\js\jquery.ajaxdispatcher.js
Dec 18 2017
Hmm.. user help at MediaWiki.org could be an example. I'm not saying it should use it but it is good enough use-case. Some wiki based on madiawiki could use it that way and I wish to use it on our wiki.
As you can see, mentioned page is placed in Category:Help with link to that category (if you look into page sources) placed out of translation, so if you switch that page to different language it will be Category:Help/de, Category:Help/ru and so on. The same for subpages. If you go to page of that category (or similar categories) it could contain some localized description and because it uses Extension:Translate it could be kept in sync across translations (Category:Help do not have description now but it was there before. Some other subcategories have it.). And if you switch between translations you can see that they already have their titles translated (so user do not see the same name that was in category-bar).
Dec 17 2017
Dec 16 2017
On my local wiki PageMigration works with Translate 2017.10 and MediaWiki 1.29.2 but with Translate 2017.10 and MediaWiki 1.30.0 it stops after first item with jQuery.Deferred exception as mentioned above
@Nemo_bis I think I found source of the problem. ext.translate.special.pagemigration.js#L145 for loop in getSourceUnits function starts from 1, but arrays are zero-based so it will always skip first translation unit, whether it is displayTitle or regular one, resulting in mentioned bug.