Wikidata:Report a technical problem/Archive/2021/12

From Wikidata
Jump to navigation Jump to search
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Is there no {{Edit semi-protected}} template?

I'm going to add some info to the talk page of an item that is semi-protected, through which to explain how a small bit of the info in the item is potentially incorrect. But i don't think that particular talk page would get seen any time soon, so i expected to be able to use {{edit semi-protected}} to add it to some generic category that keeps track of those requests... except there is no such template. What is the process i should be using in this case? -- 82.79.139.162 12:32, 1 December 2021 (UTC)

It’s called {{Edit request}} here. —MisterSynergy (talk) 13:15, 1 December 2021 (UTC)

Saint-Tropez problems

Yes in wikivoyage in spanish exists the page of Sainz-Tropez but i can not linked with the other Pages in other languages.2806:107E:12:71EA:A0BA:3FFC:19A7:65C4 04:45, 7 December 2021 (UTC)

I've connected the page to wikidata, and all now seems good. diff. --Tagishsimon (talk) 14:27, 7 December 2021 (UTC)

quadruplicate

In case you need more samples to fix this. Here are four items with identical sitelinks:

@Jura1 Thanks for these examples. We did a lot of fixes around sitelinks this year and so we do not expect to see new cases. If you do find any please let us know about it.
I looked at the revision of the examples you provided -- they all come from last year. For the old cases they would have to be fixed manually. -Mohammed Sadat (WMDE) (talk) 12:06, 22 November 2021 (UTC)
Can you run the report that identifies all of them? If there are just a few, it may be practical to do so. --- Jura 11:37, 24 November 2021 (UTC)
The two seem to be part of pile from August 2021 I just came across. --- Jura 15:25, 24 November 2021 (UTC)

Two Related Items

Items Q106091933 and Q33001013 ought to be merged, because they have categories about Piedmontese adjectives. --Apisite (talk) 01:10, 12 December 2021 (UTC)

True, but also distinctly the wrong page to report this on. I've merged them. See help:merge and if you're unable to do the merge, bring the issue to Wikidata:Project chat. --Tagishsimon (talk) 01:39, 12 December 2021 (UTC)

sitelinks to non-existing pages

Tracked in Phabricator
Task T143486

When generating w:User:Jura1/pages_with_Wikidata_items_without_any_statements from sitelinks on Wikidata, I noticed that some pages don't exist on enwiki.

Samples:

  1. w:Drought_(sport), deleted Sep 2020, still linked on Q5308627
  2. w:Ancient_Macedonian_battle_tactics, deleted Feb 2020, still linked on Q4752875
  3. w:Chordal_problem, deleted Sep 2020, still linked on Q5104977
  4. w:Dixie_Days, deleted Jan 2021, still linked on Q5284835
  5. w:Intellectual_cover, deleted Sep 2020, still linked on Q6043707
  6. w:Community_film, deleted May 2020, still linked on Q5154953

I didn't notice any on fr:Utilisateur:Jura1/articles_avec_éléments_Wikidata_sans_déclarations, but the problem is likely not limited to enwiki.

I thought the problem was resolved at some point, but it still seems to be happening.

Wikibase at Wikidata should have some feature to resync them. --- Jura 11:45, 2 December 2021 (UTC)

Indeed, this is tracked on Phab:T143486 but has not been worked on yet. Lea Lacroix (WMDE) (talk) 07:48, 9 December 2021 (UTC)
The ticket was made about a similar problem, but missing deletions don't seem to be limited to the cases mentioned.
See, e.g. Special:CentralAuth/Tone who is known to Wikidata, but whose deletion wasn't synced (see sample #1) above.
I found a few more with the reports at Q109924041 and fixed the ones for frwiki. Obviously, these reports are just a subset of all pages with that problem. @MisterSynergy: --- Jura 11:04, 15 December 2021 (UTC)

Resolve data quality issues of the sitelink system

A few data quality issues came back when dealing with claimless items. A list is (currently) at Wikidata_talk:Database_reports/without_claims_by_site/frwiki#Problèmes_identifiés/identified_issues.

A large part of remaining items seem to be due to data quality issue coming from Wikibase's dealing with sitelinks:

  • handling of redirects (or absence thereof)
  • handling of renames
  • handling of deletions
  • handling of new item creations (true duplicates)

The last one was addressed recently and this hopefully resolved the question for new items, but it seems the others aren't. The main problem seems to be that Wikibase assumes a happy path for these types of things, but sometimes this doesn't work and Wikibase doesn't attempt to resync later. --- Jura 11:25, 16 December 2021 (UTC)

There is a problem at Wikidata:Property proposal/Authority control

Hello! there is a problem at the end of Wikidata:Property proposal/Authority control, but I don't know what it may be. The last two proposals are not appearing. -Theklan (talk) 12:52, 15 December 2021 (UTC)

Hi @Theklan:, I just had a look, and I see the last few proposals ({{Wikidata:Property proposal/IRIS Marche IDs}}, {{Wikidata:Property proposal/Dicionario da Real Academia Galega}}, {{Wikidata:Property proposal/Lur Encyclopedia ID}}) appearing on the page. Do you still encounter an issue, and if so, can you describe more precisely what is missing? Lea Lacroix (WMDE) (talk) 15:03, 15 December 2021 (UTC)
I can see the links, but the template is not expanded, exactly as when the expansion limit has reached. Theklan (talk) 15:25, 15 December 2021 (UTC)
@Theklan I saw the image that you shared, but I don't encounter this issue either. Could you check your global.js and common.js and try to disable your gadgets one-by-one? (if anyone else has this problem please let us know). Mohammed Sadat (WMDE) (talk) 13:39, 21 December 2021 (UTC)

Cannot edit WD anymore using winXP + Firefox 52.9.0 since wikimedia update 1.38.0-wmf.13 (e9394e2)

Tracked in Phabricator
Task T298001

Since yesterday (16.12.2021) with wikimedia update 1.38.0-wmf.13 (e9394e2) applied I cannot edit items anymore since no edit link in Statements section show up anymore. Also the Recoin: Most relevant properties which are absent link is inactive. Only edit links showing are at the top of the page and near Wikipedia/Wikiquote/... sections. I'm still using XP with Firefox version 52.9.0. Other wikipedias updated to update 1.38.0-wmf.13 (e9394e2) do not have any problems, only wikidata. JavaScript is of course enabled but may have issues using the Wikidata User Interface. --Katpatuka (talk) 07:36, 17 December 2021 (UTC)

Hi! Unfortunately that browser is very old and falls into category C of Wikimedia's browser support now: mw:Compatibility#Browsers. This means it will not work with Java Script and unfortunately we do not yet have a way to edit statements without Java Script. Is there any chance you can upgrade to a newer browser? --Lydia Pintscher (WMDE) (talk) 10:46, 17 December 2021 (UTC)
No, since with XP has been fading out for a long time now no-one cares for old browser updates too... firefox understands javascript but seemingly not the code which came with latest wikimedia update. Is there any other WD editor you could recommend?--Katpatuka (talk) 12:40, 18 December 2021 (UTC)
The real question is not whether you can install a newer browser on XP, but whether you can install a newer operating system—XP has been unsupported for nearly eight years by now (Firefox 52 only over four years), so it may be more likely that an OS vulnerability is exploited than a browser vulnerability. For the meantime, I suggest that you do disable JavaScript either entirely in the advanced preferences or on most websites using an extension like NoScript (you can’t download it for Firefox 52 anymore from addons.mozilla.org, but the download link on the linked page points to the 5.x version that’s still compatible with FF 52). —Tacsipacsi (talk) 15:54, 19 December 2021 (UTC)
Oh of course I know I'm still running good old antique xp which is working like a charm, is fast and never crashing ;) --Katpatuka (talk) 16:58, 19 December 2021 (UTC)
I have the same problem using Safari 11.1.2 on Macintosh. With Firefox 78.15.0esr (64-bit) there is no problem. Is the Safari version too old? Wouterhagens (talk) 22:07, 17 December 2021 (UTC)
Browser console in Firefox 52 gives "Skipped ES6-only module wikibase.ui.entityViewInit" (as well as module propertySuggester.suggestions). Which makes me wonder, why is that and if this breakage is really intentional. Firefox 52, as well as Safari 10, are said to have full support for ES6[1]. Not to mention that ES6 support was added to MediaWiki itself quite recently per mw:ResourceLoader/ES6. 2001:7D0:81DA:F780:100B:8E34:9518:8CFA 08:40, 18 December 2021 (UTC)
Apparently the ES6 compatibility check includes Promise.prototype.finally, which is only supported in Firefox 58 and newer. I don’t know whether it was really part of ES6, or why was this check added (without any comment on what non-ES6-compliant browser(s) it filters), but maybe Roan Kattouw (WMF), the author of the patch, can help us here. —Tacsipacsi (talk) 15:54, 19 December 2021 (UTC)
It turns out this issue also affects Internet Explorer 11, a browser that is still supported – we’ll fix that, and this will probably make Firefox 52 work again for the time being. However, as Lydia said, it’s not a supported browser (and XP has been an unsupported OS for even longer than that), so anyone still using that browser should still find a way to upgrade regardless. (Also, due to the holidays, the fix will likely not be deployed before January.) --Lucas Werkmeister (WMDE) (talk) 12:05, 20 December 2021 (UTC)
Lucas Werkmeister (WMDE), but does the general ES6 compatibility check referenced above seem adequate? Per [2] IE 11 really doesn't support ES6, but should FF 52/Safari 11 also fail this check if they are said to support ES6? [3] suggests that aforementioned Promise.prototype.finally() was introduced in ES2018, not ES6 (2015). I see that MediaWiki formally hasn't raised its JS requirement to ES6 yet, but didn't this check already effectively raise it past ES6 to ES2018 then? 2001:7D0:81DA:F780:2C7C:8A38:97E8:FA6A 12:53, 20 December 2021 (UTC)
I think you’re conflating two different things here. MediaWiki, as a whole, still supports ES5 browsers, and the Promise.prototype.finally() check is unrelated to that. A subset of MediaWiki’s JS code (certain ResourceLoader modules) is marked with a flag called es6, which means that this code only runs on a subset of supported browsers. The bug in T298001 is that the Wikibase modules inadvertently became affected by this flag, which is why they no longer run even when we still want to support other browsers. The Promise.prototype.finally() check is part of the test whether a browser should receive es6-flagged JavaScript; you can indeed argue that the flag is misleadingly named in that case, but it’s not really the main problem here, I think. Once MediaWiki drops support for Internet Explorer 11, this feature check will probably be revisited (IE11 isn’t the only current Grade A browser that doesn’t have Promise.prototype.finally(), so we might drop support for some other browser versions too, such as Safari <11.3). Lucas Werkmeister (WMDE) (talk) 15:01, 20 December 2021 (UTC)
Alright, I probably got confused by the fact that MediaWiki on the one hand doesn't require ES6, but on the other hand supports it. Though, I still sort of wonder if Firefox 52/Safari 10+ actually can't handle any modules (other than given Wikibase module, too) with es6 flag, or are modules skipped only due to more restrictive checks. 2001:7D0:81DA:F780:49C5:1C36:8C46:47D9 15:28, 20 December 2021 (UTC)
I also cannot edit items because use XP and Google Chrome 49. Since this is a computer at my work, I cannot change the operating system myself. --Sudzuki Erina (talk) 14:50, 20 December 2021 (UTC)
I have the same problem with FF and other legacy browsers. With no perspective to change OS from Win XP in the near future, it looks like editing Wikidata is closed for me now. Or are there workarounds? Flipping Switches (talk) 18:56, 20 December 2021 (UTC)


UPDATE: We have a fix and it will be going live after the holidays once there are deployments again. We still highly encourage you to update to more modern systems wherever possible. We will not be able to fix this forever as Lucas explained and your security is at risk on outdated systems. --Lydia Pintscher (WMDE) (talk) 16:05, 22 December 2021 (UTC)

Can't add a statement to exsisting entries

Can't add a statement to exsisting entries. For example, Second Day of Christmas Q15113728 do not have such buttons--Albedo (talk) 16:10, 22 December 2021 (UTC)

Please see the discussion further up on this page about the same topic. --Lydia Pintscher (WMDE) (talk) 16:24, 22 December 2021 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Report_a_technical_problem/Archive/2021/12&oldid=1869616171"