Wikidata:Report a technical problem/Archive/2022/01

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.

Why the interlingual links of the main page of Lombard wiktionary do not work? Is there anyone able to solve the problem?--Gat lombart (talk) 15:32, 16 December 2021 (UTC)

Is it just the main page? Do some other pages like help pages work? --Lydia Pintscher (WMDE) (talk) 10:32, 17 December 2021 (UTC)
@Lydia Pintscher (WMDE): Non-mainspace pages work, see for example wikt:lmo:Wikizzionari:Portal de la comunità or wikt:lmo:Jut:Guida essenzial. Other mainspace pages on Wiktionaries, however, don’t use Wikidata, they use mw:Extension:Cognate instead. This means that mainspace on Wiktionaries is not among the namespaces where sitelinks are expected (so that Special:UnconnectedPages isn’t full of mainspace pages, the Add links doesn’t appear there etc.), and unfortunately this also means that the interlanguage links don’t appear even if the page is connected to Wikidata. Could maybe Wikibase be modified so that the interlanguage links appear even on pages in namespaces where they aren’t expected if the page is connected to Wikidata? It’s been connected for a reason, after all. If doing so on all pages has a too large performance impact, at least on main pages, as they’re always expected to have interlanguage links, in whichever namespace they are. —Tacsipacsi (talk) 19:53, 17 December 2021 (UTC)
Hmmmm. That already does work, however. Look for example at Spanish and French Wiktionary's main page. They both get their main page sitelinks from the Wikidata Item. You can check for example here: https://es.wiktionary.org/w/index.php?title=Wikcionario:Portada&action=info#Page_properties and here: https://fr.wiktionary.org/w/index.php?title=Wiktionnaire:Page_d%E2%80%99accueil&action=info#Page_properties Compare that to https://lmo.wiktionary.org/w/index.php?title=Pagina_principala&action=info#Page_properties. I tried seeing if there is any page overwriting or suppressing the language links for the main page on Lombard Wiktionary locally but I can't find anything because I don't understand enough of the language. Is this maybe something that can help you investigate further? --Lydia Pintscher (WMDE) (talk) 16:23, 22 December 2021 (UTC)
@Lydia Pintscher (WMDE): Look at the titles—the Spanish and French main pages are in the project namespace, which, as I wrote above, works on Lombard Wiktionary as well. Choosing a few main pages from Q5296#sitelinks-wiktionary that are in the main namespace, Afrikaans, Belarusian, Divehi, Hebrew, Kurdish, Oromo, Albanian and Zulu don’t have Wikidata item ID in page info either. (Some of them do have interlanguage links, but these are thanks to local wikitext interlanguage links, not Wikidata.) —Tacsipacsi (talk) 17:56, 22 December 2021 (UTC)
@Tacsipacsi Urgh you're right. Sorry I missed that. Alright. Does anything speak against Lombard Wiktionary doing one of the things these other Wiktionaries are doing? As much as I'd like it to be different I don't think we'll be able to spend time on a more complex special-casing for this unfortunately. -- Lydia Pintscher (WMDE) (talk) 17:06, 26 December 2021 (UTC)
I am sysop on Lombard wiktionary. If I can help you in something about Lombard language you can ask me--Gat lombart (talk) 21:31, 26 December 2021 (UTC)
Can't it be helpful reporting a bug to phabricator?--Gat lombart (talk) 21:33, 26 December 2021 (UTC)
Thanks a lot for the offer, @Gat lombart :) The ticket at phab:T210784 should be sufficient. Lydia Pintscher (WMDE) (talk) 09:21, 6 January 2022 (UTC)
@Lydia Pintscher (WMDE): I can’t speak on behalf of Lombard Wiktionary, but since many wikis are affected (about two thirds of Wiktionary main pages are in the main namespace if my query [...document.querySelectorAll('div[data-wb-sitelinks-group="wiktionary"] .wikibase-sitelinkview-page a')].map(a => a.title).filter(t => t.indexOf(':') === -1).length / document.querySelectorAll('div[data-wb-sitelinks-group="wiktionary"] .wikibase-sitelinkview-page a').length is correct), I think it should be fixed in software instead of working it around on over a hundred wikis. I found phab:T210784, which seems to be the same root cause. (By the way, why are you here, Lydia? Isn’t Second Day of Christmas (Q15113728) a holiday in Berlin as well? Merry Christmas anyway!) —Tacsipacsi (talk) 00:30, 27 December 2021 (UTC)
@Tacsipacsi: Haha yes. But you know how it is with the wikis. They never sleep ;-) Happy New Year!
As for fixing the underlying issue: Yes I agree this would absolutely be better. I'm just being realistic that this is not something I can currently prioritize very highly. Too many things to do :( It sucks. Lydia Pintscher (WMDE) (talk) 09:23, 6 January 2022 (UTC)

Missing language options

Where a language label is required to label a string (such as on 'title' or 'first line'), could you please expand the list of options to accept any valid language code from the IANA subtag registry (browsable via the BCP47 language subtag lookup app)? Many smaller languages are missing from the list of available options when editing Wikidata, ranging from Diuxi-Tilantongo Mixtec to Old French. AndrewNJ (talk) 06:37, 1 January 2022 (UTC)

Hello @AndrewNJ:, we can add new language codes for monolingual text on request, if you explain the use you would make of it. Please see Help:Monolingual text languages, especially the "Getting a language code added" section. On this Phabricator board, in the "Wikidata (monolingual text)" column, you can see some pending requests. Let us know if you need support. Lea Lacroix (WMDE) (talk) 15:34, 4 January 2022 (UTC)

Does Wikidata test instance work properly?

Hi, since days I fail to edit items on Wikidata test instance. It may be due to my own inability, however, I would just like to be sure, that it's not a general problem. I already asked in project chat but got no answer. I was asked to bring up the question here. see: https://www.wikidata.org/wiki/Wikidata:Project_chat -> permission to wikidata test instance? https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Bot/Orcbot#Orcbot

This is my config file:

  {
    "instance": "https://test.wikidata.org",
    "credentials": {
      "https://test.wikidata.org": {
        "username": "bot@bot",
        "password": ".."
      }
    }
  }

this is the statement to edit the test instance using wikibase-cli:

    wb create-entity item.json

this is the beginning of the error message:

  { permissiondenied: permissiondenied: You do not have the permissions needed to carry out this action.
  at requestError (/usr/local/lib/node_modules/wikibase-cli/node_modules/wikibase-edit/lib/request/parse_response_body.js:18:15)
  at module.exports (/usr/local/lib/node_modules/wikibase-cli/node_modules/wikibase-edit/lib/request/parse_response_body.js:11:33)
  at process._tickCallback (internal/process/next_tick.js:68:7)
  url: https://test.wikidata.org/w/api.php?action=wbeditentity&format=json
  response status: 200 }

Thank you very much in advance! --Eva (talk) 13:09, 19 January 2022 (UTC)

Test Wikidata is supposed to work in general, and testwikidata:Special:RecentChanges also shows some edits by others. I’m not sure why you would get a permissiondenied error; can you paste your item.json and more of the error message somewhere (e.g. https://paste.toolforge.org/)? Lucas Werkmeister (WMDE) (talk) 15:19, 19 January 2022 (UTC)
Hey @Lucas Werkmeister (WMDE): here you can find the complete error message: https://paste.toolforge.org/view/0d87d3e6
This is the item.json: https://paste.toolforge.org/view/751ac45a
Thank you! Eva (talk) 10:20, 20 January 2022 (UTC)
@EvaSeidlmayer Are you maybe using a bot password that doesn’t include the “Create, edit, and move pages” grant? Lucas Werkmeister (WMDE) (talk) 11:04, 20 January 2022 (UTC)
Actually, this was the reason! So easy! Thank you!!! Eva (talk) 13:41, 20 January 2022 (UTC)
Great! :) Lucas Werkmeister (WMDE) (talk) 17:33, 20 January 2022 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Lucas Werkmeister (WMDE) (talk) 17:33, 20 January 2022 (UTC)

1,500 character limit on strings

Hi - I have been adding various properties to all Public General Act of the Parliament of the United Kingdom (Q105774620), Act of the Scottish Parliament (Q18009506) and so on, and I have run into the 1,500 character limit on strings when adding the official name (P1448) (or "long title") to a few Acts, because they're extremely long. These are (largest to smallest):

Is it possible to get the limit raised for this property? I anticipate that this may also happen for a few Act of the Parliament of the United Kingdom (Q4677783), Act of Senedd Cymru (Q4676706) and Act of the Northern Ireland Assembly (Q100271152) etc. Theknightwho (talk) 22:02, 20 December 2021 (UTC)

Treaties, also: notorious for ridiculously wordy titles. But yes, I've had to truncate a few Acts. (And, different subject, truncate labels for e.g. Statutory Instruments, some of which (roadworks, mainly) don't fit. --Tagishsimon (talk) 11:30, 24 December 2021 (UTC)
Tagishsimon - if you're curious, I've fudged it by splitting up the titles into parts, and then used the qualifier nature of statement (P5102) with the new item "value split up, due to exceeding the 1,500 character limit on strings (Q110418529)", followed by series ordinal (P1545). Obviously not ideal, but it's a way to at least get the relevant info onto the items for now, pending a better solution. Theknightwho (talk) 02:15, 5 January 2022 (UTC)
@Theknightwho We have raised the limit in the past based on user requests. But,
  • is increasing the limit the right solution to this problem?
  • what should we increase it to?
To accommodate the acts you listed for example, we’d need about 3000 characters - that’s already double what the current limit is. One of the advantages of keeping the limit low is so we do not start having copyrighted texts in certain properties like poems. Are there other solutions to consider that do not involved increasing the limit, like splitting up the titles into parts as you already did? -Mohammed Sadat (WMDE) (talk) 09:28, 7 January 2022 (UTC)
Hi, and thanks for the response! In this case, would it please be possible for you to raise the limit to 3,000 characters? There are three reasons for this:
  1. From a practical perspective, these are the full titles, and technically have precedence over anything else. There is no way to abbreviate them that would be accurate, and they serve an important purpose in being able to interpret the legislation.
  2. While it is possible to split them (as I have), this makes querying them considerably trickier. My intention is to re-code the Lua module I created on the English Wikipedia that is powering the lists of UK legislation (such as this one), which do include the long title. It would be quite a bit of extra work to have to rely on querying for qualifiers etc., for what is only a tiny proportion of the total number.
  3. There should be no issues with copyright, as these are all covered by the UK government's Open Government Licence (Q17016921). Anything prior to 1972 is public domain, as Crown Copyright in this case is 50 years.
As far as I can tell, Act titles have been trending towards getting longer in recent years, so I don't anticipate anything even longer cropping up while I work backwards, as I have now uploaded all Acts dating back to 1960.
Theknightwho (talk) 09:50, 7 January 2022 (UTC)
@Mohammed Sadat (WMDE) - it’s just occurred to me that maybe we could implement an abuse filter that triggers if a string above a certain length is added? Alternatively, maybe there could be a form of manual approval required if someone makes edits above that length? In both cases, that could ensure that only a small number of items end up with very long strings, and only when it’s an inherent part of the item’s metadata (e.g. the title), and therefore not at risk of violating copyright by being gratuitous. Theknightwho (talk) 01:30, 8 January 2022 (UTC)

I want ask about wrong link when click Main Page or Kaca utama in Balinese version, What should I do to fix this??

Chinamoonroll (talk) 08:48, 25 December 2021 (UTC)

You should change MediaWiki:Mainpage/ban. 217.117.125.83 14:50, 27 December 2021 (UTC)
Thanks for information, that must "Wikidata:Kaca Utama", but i don't have permission to edit on Wikidata or Translatewiki. Chinamoonroll (talk) 01:24, 9 January 2022 (UTC)

SVG export from WDQS don't work

Dear editors, please, help. I have a SPARQL query - colored graph of astronauts and space ships. I want to download an SVG image of the graph (in order to upload to Wikimedia Commons), but the button "SVG" don't work. Could you help me? --Andrew Krizhanovsky (talk) 16:10, 8 January 2022 (UTC)

@AKA MBG: Unfortunately the SVG export only works for a subset of result views (mainly the chart-based ones, I believe), and the graph view is not one of them. --Lucas Werkmeister (WMDE) (talk) 10:50, 10 January 2022 (UTC)

Mistake Q30527586

i do not know english. https://www.wikidata.org/wiki/Q30527586 This page is redundant. The link to this page should be moved: https://www.wikidata.org/wiki/Q568375 See my remarks on the talk page: https://www.wikidata.org/wiki/Talk:Q30527586 ילד מסכן וחכם (talk) 10:15, 9 January 2022 (UTC)

@ילד מסכן וחכם: ✓ Done See Help:Merge for future cases of redundant items. --Epìdosis 12:12, 9 January 2022 (UTC)

"Edit" option issue.

I hope this is the correct place to address this issue.

When I look at a wikidata item page, all the properties are listed. With a grey background we first have the property name, and to the right of it with a white background the property value. Behind the value the "edit" option is shown.

I work with an increased fontsize of 125% (using CTRL-+) on my screen. Most properties have a value in text format. The increased fomtsize causes some values to be wrapped over 2 or more lines. This os not a problem. However for the image property (P18) there is a problem. An image cannot be wrapped so as a result the "edit" option is moved outside the screenview. The "edit" option getting moved outside the screenview wouldn't be a problem either if a horizontal scrollbar would appear. But the scrollbar doesn't appear and therefore it It seems as if the "edit" option doesn't exist for the image property. This I consider to be a bug, not the most problematic one, but it is a problem imo. If I increase the fontsize even more (in my case to 150%) the "edit" option reappears in the top left corner of the image. When I increase even more (175%) part of the image is moved out of the screenview as well. Only at that time the horizontal scrollbar appears. However I can scroll only far enough to the right to make the full image visible but not even further to the right to see the "edit" option as well. Two additonal increases (250&), when the full image ends up outside the screenview, the "edit" option reappears again. However it's shown in front of the property name (not value). Of course, not likely someone will increase the fontsize to 250%, but I'm probably not the only one with an increase of 125%. At such an increase the "edit" option should either be visible (e.g. below the image) or it should be possible to make it visable using the horizontal scrollbar. --Sb008 (talk) 13:06, 5 January 2022 (UTC)

Hello @Sb008! Thanks for reporting this issue and describing it in detail. We’re aware of the wrapping problems in the UI. Unfortunately this issue with the edit button moving out of the screen view cannot be tackled in isolation but should be fixed as part of the ongoing design and component development we’re doing this year. -Mohammed Sadat (WMDE) (talk) 10:03, 11 January 2022 (UTC)

Lost in Translation

As an native German-speaker with moderate English-skills, I frequently fumble over translation problems, where a word in one language has two in the other. This becomes apparent, if you check the English topping lift (Q607634) finding its equivalent in the German "Toppnant", but also in the German "Dirk" (Q11694269). The reason is, that German differentiates between the main-sail boom and the spinnakerboom. Besides my limited English-skills, I'm no IT-crack either, so I don't know if there is a potential fix for this type of problem. However, it would be a significant improvement over the current situation for Interwiki-links. The problem is not limited to German-English translations. If you need more examples, I'd be willing to assist in the search. Yotwen (talk) 06:24, 10 January 2022 (UTC)

Hi @Yotwen. This sounds to me like an editorial issue. Please discuss it with the community on the Project chat. -Mohammed Sadat (WMDE) (talk) 10:02, 11 January 2022 (UTC)

Reasonator

Reasonator somewhy doesn’t show anything except of header for some time (I don’t remember exactly, weeks or months.). FireFox 93.0 EME-free x64, Windows 10 2004 x64 217.117.125.83 17:39, 25 December 2021 (UTC)

See the above discussion about functionality for non-ES6 browsers. A fix is on the way. -Mohammed Sadat (WMDE) (talk) 09:47, 5 January 2022 (UTC)
@Mohammed Sadat (WMDE): Are you sure that it’s about my problem? My browser is new and I can edit items but I have problem with the button too. 217.117.125.83 10:50, 5 January 2022 (UTC)
I’m sure it’s not about your problem. For me (Firefox 91.4.1esr and 96.0b10 on Debian 10), https://reasonator.toolforge.org/?q=Q42 loads, but quite slowly (over half a minute until actual data appears). Is this particular URL broken for you? If yes, you might want to look at your browser extensions. Ad blockers and security extensions (like NoScript or security software’s extensions) often can cause issues, but you should check other extensions as well. —Tacsipacsi (talk) 22:37, 5 January 2022 (UTC)
@Tacsipacsi: I have been waiting for 6 mins but nothing have loaded. I have only one content‐blocking extension (adblocker) and it’s disabled for the site. 217.117.125.83 16:30, 6 January 2022 (UTC)
And other, non-content-blocking extensions? They’re less likely but not impossible to cause issues. You may also look at your browser console. By the way, the latest stable version of Firefox is 95.0.2 (at least in the normal, not EME-free version), aren’t you able to update? —Tacsipacsi (talk) 11:42, 11 January 2022 (UTC)
  • FoxyTab
  • No PDF Download
  • Tab reloader
  • Zoom scheduler
and search engines
Console says only Uncaught ReferenceError: wd_auto_desc_wd is not defined.
I believe that my FireFox version is still new. 217.117.125.83 17:13, 29 January 2022 (UTC)
@217.117.125.83 Are you still experiencing this issue? If so then I'm afraid you will have to file a report with the developer as Reasonator is a community developed tooI. -Mohammed Sadat (WMDE) (talk) 11:49, 11 January 2022 (UTC)
Yes, I am. @Magnus Manske 217.117.125.83 17:08, 29 January 2022 (UTC)

Can you solve the translation problem and the update problem?

I know that Wikidata has a disadvantage of having translation problems and slow updates, so I don't have enough time to solve them.

However, I think we need to go through the steps that require development.

I think development should continue.

Can Wikidata handle all of this? Takuyakoz (talk) 11:13, 25 January 2022 (UTC)

Hello @Takuyakoz ! Please clarify what translation and update problems you mean. -Mohammed Sadat (WMDE) (talk) 12:07, 31 January 2022 (UTC)

Statements without properties ??

I was exploring the sparql endpoint searching for values with upper and lower bound not centered around the origin and found something weird.

I followed the link availables on this query : https://query.wikidata.org/#describe%20wdv%3A80dd3a11db184aa7ae34c3025adfa89d author  TomT0m / talk page 19:18, 29 January 2022 (UTC)

@TomT0m: That’s an unfortunate interplay of T285694 and MediaWiki talk:Common.css#Styling Deprecated/Preferred Ranks, see T285694#7662954. Lucas Werkmeister (WMDE) (talk) 10:58, 31 January 2022 (UTC)

could we properly alphabetize WP links?

The languages in the WP links are consistently out of order, in that most 3-letter language codes will come before a 2-letter code. I'm constantly forgetting that and sometimes conclude that the article doesn't exist in the WP I'm looking for. (E.g. if I scroll down so that the link I'm looking for is off the top of the page, but I can still see the link should be alphabetized before it.) Can this be fixed?

It's not 100%, but happens most of the time. E.g.

ang > an; ban, bat > ba; csb > cs; fiu > fi; frr > fr; gan > ga; hif > hi; jam > ja; kab > ka; koi > ko; ksh > ks; lbe > lb; lij > li; mni > mn; mrj > mr; myv > my; nds_nl > nds; pap > pa; rue > ru; sah > sa; scn, sco > sc; war > wa; zh_... > zh; but ar > ary, arz; hy > hyw; and ne > new.

From the exceptions, it looks like correct alphabetization only occurs when the 3rd letter is {w x y z}. Kwamikagami (talk) 06:12, 31 January 2022 (UTC)

@Kwamikagami: I think if you disable the “Site ID to interwiki” gadget, the order will make more sense. On Wikimedia main page (Q5296), I see: amiwiki, amwiki, angwiki, anwiki, arcwiki, arwiki… mlwiki, mniwiki, mnwiki, mnwwiki, mrjwiki, mrwiki… it is alphabetical, at least until the gadget changes the displayed text without adjusting the order. Lucas Werkmeister (WMDE) (talk) 12:19, 31 January 2022 (UTC)
Ah, that makes sense. Thank you. Kwamikagami (talk) 12:42, 31 January 2022 (UTC)