Since these parameters indeed both have the same alias, isn't that as desired? In practice, only parameters, not aliases, are offered by the GUI interface for Template Data anyway - I think aliases are just for documentation reasons mostly?

Re-opening as some of them still have the PMC and this is inconsistent, i.e. 10.1186/1471-2148-7-97

Another complaint about this here: https://www.mediawiki.org/wiki/Topic:V6u2mpy11qiu9705

In T232954#5494396, @matmarex wrote:

I remember that at some point in the migration to HHVM we discovered that HHVM's JSON parser was less strict than PHP's, and allowed the trailing commas. I don't remember if we did anything about that, but it might be the same problem?

Dupe of T190850, I think.

Note that I also found that I can't set the values of the rest API through the page (api), but I can create the url directly.

For future reference, you can see here that the results are coming from Zotero:

In T229654#5403601, @matmarex wrote:

I asked to pull this into "Investigating" because I was very confused by the description. I think it was missing a "not", please check if that's right. Also, the issue is not reproducible at the given URL anymore, because Citoid was apparently enabled on the wiki. Is there another example?

In T228576#5354334, @Effeietsanders wrote:

In T228576#5352847, @Nikerabbit wrote:

For debugging, it would be really helpful if you could give message ids in copy-paste format.

Just to be clear: is that a request for now, or for future reports?

I think maybe for the future.

This is a big issue for wikibase integration too; at present wikidata has a constraint that the isbn be hyphenated, but in reality some records lack the hyphenation despite the constraint. Thoughts? We need to pick one and stick with it.

So the short answer is - yes, that'd be ideal. But the ISBN situation is kind of a disaster though. The hyphenation position depends on knowing the length of other elements, like registration group, and these change so they need to be *constantly updated in order to correctly hyphenate them.*

With the new patch I'm now getting

I've just quickly fixed the config; it was relatively simple as hi wiki uses all the same templates as en wiki so I just copied some stuff over. Should all be working now!

You've also found a bug, we shouldn't be offering the "convert" option if citoid isn't correctly enabled. Thanks for the reporting! I've separated that off into T229654.

I've temporarily disabled it here, as it is incorrectly configured: https://hi.wikipedia.org/w/index.php?title=%E0%A4%AE%E0%A5%80%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A4%BF:Citoid-template-type-map.json&action=history

In T228503#5383302, @Smalyshev wrote:

I tried to install wikibasecirrussearch with vagrant and it seems to work for me, after manually enabling $wgWBCSUseCirrus = true; (that part is not automatic yet). Maybe some other configurations are interfering? Are there any local configs and where do you configure $wgWBCSUseCirrus = true;? Did you check that you have latest master checkout of all modules (CirrusSearch, Wikibase, WikibaseCirrusSearch)?

The technical name of the tab was been changed in T219512, so I think the message just needs to be re-translated to use the new name (citoid-citoiddialog-mode-manual) on https://translatewiki.net/

In T214038#5300696, @JTannerWMF wrote:

What would be involved in implementing your suggestion of automatically rerouting people to citation template? How often does this happen @mvolvz, the copy tweak makes sense in the mean time.

No longer getting this, so closing.

In T227766#5324739, @Legoktm wrote:

Is there a replacement target, or should it just be removed outright?

In T206613#5311274, @Smalyshev wrote:

I've reindexed testwikidata last week, the patch should already be there.

This is affecting Citoid as well, see T227415.

Probably same problem as: T226088

Which is to say, my response there on that thread was to the first comment, but not to the later report of the all of pubmed being down, as these are two separate issues- I should have read the whole thread instead of just the first message! Thanks for tagging this @Aklapper so it reached my attention again, definitely not good.

In T227415#5311732, @Aklapper wrote:

See the reply in https://www.mediawiki.org/w/index.php?title=Topic:V2pf99neqh2qupud&topic_showPostId=v2sd70b9r9165l32#flow-post-v2sd70b9r9165l32

We're going to try to deploy this first on test.wikidata, can this be reindexed as well? Or do they both get re-indexed at the same time?

I'm not sure whether to resolve or decline this as Research wasn't involved here :).

No worries; I wasn't aware the train was broken and wondered if the
reindexing had to be triggered manually or something, thanks for the update!

In T206613#5235476, @Smalyshev wrote:

Now after it's deployed reindex will be needed.