Jump to content

Wikidata:Report a technical problem

Add topic
Shortcut: WD:RATP
From Wikidata


Report a problemHow to report a problemHelp with PhabricatorGet involvedWDQS and Search

Start a new discussion

MediaWiki:Wikibase-SortedProperties - move external-ids to MediaWiki:Wikibase-SortedPropertiesIDs

[edit]

As of today MediaWiki:Wikibase-SortedProperties contains 12880 lines. The section "== IDs with datatype "external-id" ==" starts at line 3304.

Separating the external-IDs to a new page MediaWiki:Wikibase-SortedPropertiesIDs provides for:

  • diffs, each focused on only one of the sets
  • talk pages, each concerning only one of the sets
  • shorter pages
  • optional special treatments of the sort mechanisms,
    • e.g. external IDs could be sorted by English label by default, or any other language specified somewhere. Tthe language does matter less here, since the ID labels sort mostly the same, independent of language, Romance languages have the order "identificator XYZ", Germanic languages often "XYZ identifier", so sorting by English would sort by XYZ, by a Romance language it would first group by "identificator" - but the English sort logic would be understandable.
    • if external IDs fall into the group "=== Other IDs with type "external-id" - alphabetical order ===" (9281 lines) - they could potentially be removed from that page completely
    • the list of external IDs on item pages could optionally show the titles of the section's used to group the IDs and make reading the list easier.

Maybe also other output apart from HTML can benefit. OSMan2025 (talk) 16:19, 9 October 2025 (UTC)Reply

Hi OSMan2025, thanks for the detailed suggestion. The property order system doesn't parse wikitext transclusions, so splitting the content while maintaining functionality isn't straightforward. This would also be a significant technical change for what appears to be minimal improvement. Are there specific parts in there that are particularly difficult to work with? We'd be happy to explore more targeted solutions for those. -Mohammed Abdulai (WMDE) (talk) 09:59, 3 November 2025 (UTC)Reply

Changing datatype for a property

[edit]

It has been requested on Property talk:P12889 twice that the datatype be changed from string to external-id. LGTM. Infrastruktur (talk) 11:02, 10 October 2025 (UTC)Reply

Thanks for the report. LennardHofmann has included it in this request , so we now have enough Properties to run the script for all of them together. -Mohammed Abdulai (WMDE) (talk) 11:01, 13 October 2025 (UTC)Reply
It says more support is needed because sockpuppets participated in the discussions, but I think Skype username (P2893) should be converted - a username is an identifier, it just has continuously changes / unstable identifier (Q23611587). I'm less certain about URL-based identifiers such as myfixguide.com ID (P12889) and page at OSTIS Belarus Wiki (P2490), and about OpenStreetMap tag (P1282), which I think was not originally intended as an identifier but seems to function as one now, but I don't oppose the requests. Another property I have noticed that should have been an identifier is TÜİK neighborhood ID (P12883) - I assume it was just copied from Wikidata:Property proposal/Tüik number where I suggested separate properties for each type of administrative unit as the intended use required an identifier. Peter James (talk) 11:29, 26 October 2025 (UTC)Reply

Dark mode

[edit]

Hello,

On Q170412#P18, the value of P18 (musical score) is not displayed in dark mode.

Cordially. —Eihel (talk) 14:23, 21 October 2025 (UTC)Reply

That’s a PNG image, not a musical score value. Lucas Werkmeister (WMDE) (talk) 15:29, 21 October 2025 (UTC)Reply
I don't quite understand your answer, Lucas Werkmeister (WMDE). The png image illustrating this element are notes on a musical staff. However, the image is still not visible in dark mode. That's why I added this section and I think we should focus on this fact instead. —Eihel (talk) 01:17, 22 October 2025 (UTC)Reply
Perhaps I should notify an interface admin directly: Putnik Eihel (talk) 01:19, 22 October 2025 (UTC)Reply
When there is an image like this on Wikipedia, we can add class=skin-invert-image. But this is not possible on Wikidata. Unless there is supported a similar mechanism on Wikidata, the images will display like this in dark mode and thus this is not actionable for interface admins either. --Matěj Suchánek (talk) 06:24, 22 October 2025 (UTC)Reply
@Eihel, I'm not sure I understand what you mean by "is not displayed." Black notes on a black/dark background? A white/light rectangle instead of an image? Just an image with a light background in dark mode? If the latter, then, as has already been answered, it is impossible to come up with a single rule for all images. If it's something else, then it's a bug, and please specify which browser this behavior occurs in. —putnik 08:48, 22 October 2025 (UTC)Reply
@Eihel: Ah, now I see the problem. I had tried Vector 2022’s dark appearance option, where the score shows in black-on-white, so it wasn’t clear to me what your problem was and I thought you wanted the score to be inverted to white-on-black. Using the dark mode toggle gadget, it appears as black-on-black instead (because the PNG is transparent and the gadget, unlike the skin, doesn’t add a solid white background to it). I agree this is an issue, but it sounds like it needs to be fixed in the gadget. Lucas Werkmeister (WMDE) (talk) 09:16, 22 October 2025 (UTC)Reply

changing label/description on same item (in another tab) gives duplication error

[edit]

This is practically a non-issue but I'll raise it anyway.

If one opens the same item twice, as to have it open in two tabs, and you change the label or description in one, then again in the other, you recieve the error:

"Could not save due to an error. Item Q12345 already has label "xyz" associated with language code en, using the same description text"

This is technically incorrect as it is the exact same Q item that has the same label or description. Whether this is worth anyones time to fix, or even how to fix it, can be up to anyone who works on the code for this project. :) Tæppa (talk) 23:22, 3 November 2025 (UTC)Reply

Hi @Tæppa. Thanks for writing here. This is actually on our radar. See the linked tickets above. -Mohammed Abdulai (WMDE) (talk) 15:09, 18 November 2025 (UTC)Reply