Page MenuHomePhabricator

Userscripts relying on VIAF not working anymore in Wikidata
Closed, ResolvedPublicBUG REPORT

Description

Steps to replicate the issue:

importScript( 'User:Bargioni/moreIdentifiers defaultconf.js' );
importScript( 'User:Bargioni/moreIdentifiers.js' );
importScript( 'User:Bargioni/viaf.js' );

What happens?:

  • the content of the VIAF cluster(s) is not loaded in the box "Add More Identifiers from VIAF" (which is generated by moreIdentifiers.js)
  • hovering on the VIAF ID(s) you don't see a preview of their content (which is generated by viaf.js)

What should have happened instead?:

  • the content of the VIAF cluster(s) should be loaded in the box "Add More Identifiers from VIAF"
  • hovering on the VIAF ID(s) a preview of their content should be seen

Cf. documentation https://www.wikidata.org/wiki/User:Bargioni/moreIdentifiers

Note: according to https://www.wikidata.org/wiki/Wikidata:Database_reports/Gadget_usage_statistics/wikidata moreIdentifiers is the most used common.js gadget in Wikidata, with 316 active users using it; it is highly relevant in the workflow of users involved in authority control activities

Probabile cause:
These userscripts load data from viaf.org; a few hours ago most userscripts were reenabled (cf. T419154); however, I think gagets loading data from non-Wikimedia websites might be affected by "some hopefully-not-too-intrusive, temporary restrictions" (cf. T419154#11679745); since I haven't found a public ticket about these restrictions, I open this

Event Timeline

I've cross-posted about this in the appropriate private ticket.

We plan to unbreak this by updating our allowlist - thanks for flagging.

It is better to open a separate ticket (but you could include all of them at once in it).

We are now supporting viaf.org within the enforcing CSP, which hopefully unblocks this issue. (relevant config patch)

Thanks @sbassett I confirm the gadgets now restarted working; @EMill-WMF OK I opened T419285 for these 3 library catalogs.