The work for adding favourite templates will be done in T367428 and its subtasks. There's no roadmap right now for adding recently-used, but there is a plan to investigate that after the favouriting feature is done.

I had to revert 1080830 due to an exception "can't convert null to object"

I see the issue, but I'm not quite sure what input from UploadWizard caused it.

I think possibly the recent change to uw.deed.OwnWork.js is perhaps now breaking the case in which the upwiz_licensename preference is a custom value. For example, I've got that preference set to a template (which has worked fine for years), but it's now ending up with this sort of thing: |author=[[User:Samwilson|{{User:Samwilson/photographer|camera=}}]] which isn't correct. Maybe that preference isn't meant to be arbitrary wikitext, but if that's true then it should say so. Maybe this is a case of XKCD #1172.

Okay, let's expand this task to include adding the button to everywhere it'll be needed.

I think this is all done for now. There are more messages to move, and of course be more edits to them as we migrate other bits to the extension, but that can all be done as part of the relevant tasks I think.

I've updated the task a bit, to make it less about specific API calls and hopefully more informative.

Oh yep, and I'll update the description with the correct detail about how TemplateWizard works (with and without CirrusSearch).

@thiemowmde Yep, we're aiming to not change anything at all, at least initially. I was just confusing myself about the asterisk and thinking that it wasn't necessary! Oops.

Why do we do the prefix search at all? Why not just do a namespace search in all cases? My recollection is that, back when we were building TemplateWizard, prefix search was preferred because many wikis have conventions around template names, so it makes it possible to find all cite templates by starting to type cite, or infoboxes with infobox. I feel like that might be out of date now, and that having the same search results in the template dialogs (the same as what you get at Special:Search?ns10=1) might be more expected. We have been talking a bit about using CirrusSearch if it's installed, but it looks like the only thing we're doing is the asterisk at the end of the search term, which seems to be an attempt to emulate a prefix search.

I don't think that'll be part of the first round of work, but it's definitely something that's come up and will be considered more properly after the basic functionality is done.

Oh sorry, no there's also the langlinks and langlinkscount API results.

I've added some documentation about this feature: https://www.mediawiki.org/wiki/Extension:UnlinkedWikibase#Interlanguage_links (please edit as you see fit).

I think this might be to do with session storage, because the 2nd request access is only prevented for the same session — for other users it looks to be working fine.

The fixes here seem to be either

• give the table a background color so that although it obscures the tools menu its contents can at least been read clearly; or
• constrain the width of the table.

@AlphaLemur I finally got around to finishing this, you can see it in action here: https://wikimedia.org.au/wiki/MediaWiki_skin#Cards