- Wikibase Community User Group - lists.wikimedia.org

Configuring prefixes in WDQS service
by Aidan Hogan 06 Mar '26

06 Mar '26

Dear all, Recently I updated my Wikibase instance to use WBS Deploy 5.0.1. I think I have resolved almost all of the issues post-update, except for one. The pre-loaded SPARQL query prefixes on the WDQS front-end maintain their Wikidata values. The query service is here: https://query.qawiki.org/ The WDQS custom config can be seen here: https://query.qawiki.org/custom-config.json The query SELECT (STR(wd:Q1) AS ?iri) WHERE {} returns http://www.wikidata.org/entity/Q1 Queries using new / non-standard prefixes fail for using an undefined prefix. I've searched around, but cannot find much documentation about this. Would appreciate it a lot if anyone can provide pointers on how to configure the prefixes used in the WDQS front end (and back end if necessary)? Best/thanks, Aidan

4 5

Wikibase Suite Deploy 6.0.0 and Wikibase Image 6.0.0 (MediaWiki 1.45)
by Deepesha Burse 02 Mar '26

02 Mar '26

Dear Wikibase Community, We’re happy to announce Wikibase Suite Deploy 6.0.0 as well as Wikibase Image 6.0.0 today! The biggest highlight of this release is the switch to the latest version of MediaWiki: 1.45. Read about MediaWiki 1.45 in their changelog <https://www.mediawiki.org/wiki/Release_notes/1.45>. This release also includes a Wikibase Suite version reporting feature in Special:Version and via the Action API. More details are mentioned in the changelogs for Wikibase Suite Deploy <https://github.com/wmde/wikibase-release-pipeline/blob/main/deploy/CHANGELO…> and Wikibase <https://github.com/wmde/wikibase-release-pipeline/blob/main/build/wikibase/…> . InstallationNew installation To install Wikibase Suite Deploy, follow the instructions in our documentation <https://github.com/wmde/wikibase-release-pipeline/tree/main/deploy#initial-…> . Updating from earlier versions of Wikibase Suite Deploy For information on how to upgrade from earlier versions of Wikibase Suite Deploy, check out our upgrading documentation <https://github.com/wmde/wikibase-release-pipeline/blob/main/deploy/1-updati…> . Got feedback or questions? Join our channels on Telegram https://t.me/wikibasesuite and https://t.me/+WBsf9-C9KPuMZCDT. You can also check out our Phabricator board at https://phabricator.wikimedia.org/project/view/5755/. You can go through our privacy policy <https://www.wikimedia.de/datenschutz/#dataprivacy> for more information. Want to stay up to date? Sign up for our mailing list to follow and participate in discussions about Wikibase development: https://lists.wikimedia.org/postorius/lists/wikibaseug.lists.wikimedia.org/ Best, Deepesha, on behalf of the WMDE Wikibase Suite team -- Developer Advocate Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30-577 11 62-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland — Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Charlottenburg, VR 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine.

1 0

Re: Cara Buka Blokir wondr BNi Mobile banking
by Sare Kite 17 Feb '26

17 Feb '26

1 0

Problems migrating Wikibase instance to HTTPS
by Aidan Hogan 17 Feb '26

17 Feb '26

Hi all, I am running a Wikibase instance at https://qawiki.org/ via Docker. The version I am running is wikibase-bundle:1.36.3-wmde.4. (I considered updating to the latest version, but it seems daunting.) I've recently switched to HTTPS hosting, but have not managed to get the Wikibase config working fully. I wish to keep HTTP IRIs for the RDF/SPARQL service (otherwise the WDQS updater skips all entities and/or if I force HTTPS, the query service still uses HTTP prefixes), so I set in LocalSettings.php: $wgServer = "http://qawiki.org"; $wgCanonicalServer = $wgServer; To enable HTTPS elsewhere, I've tried setting: $wgWBRepoSettings['repoApiBaseUri'] = 'https://qawiki.org/w/api.php'; $wgSecureLogin = true; $wgCookieSecure = true; $wgUsePathInfo = true; $wgResourceLoaderStorageVersion = 2; Everything is mostly working okay, except some API calls are directed to HTTP, and fail due to mixed content. For example, visiting: https://qawiki.org/ and tying "w" in the search bar should provide autocomplete suggestions, but the call is heading to: http://qawiki.org/w/api.php?action=wbsearchentities&search=What%20is%20the&… and is being blocked for mixed content. I don't know why it generates a HTTP URL, but I guess it relates to $wgServer. If I set $wgServer to HTTPS, these issues disappear, but then the WDQS updater no longer works, and if I manually update with --conceptUri https://qawiki.org/ the WDQS prefixes still use HTTP, and it breaks some application queries. Any help on how to "force" the front-end to call the API via HTTPS (ideally without changing $wgServer, which seems to break WDQS) would be appreciated! Best, Aidan

5 8

Recent list spam
by Laurence Parry 14 Feb '26

14 Feb '26

Looks like some spam got through whatever filters WMF have in place. New membership and posts will be held for moderation for the moment. Apologies for any inconvenience. [Before anyone asks why the spam is still there for right now: list owners- as opposed to mailman admins/WMF SREs - can't yet remove messages from the archive. It requires the *next* version of Hyperkitty... which is most likely to become after the list server is updated to Debian Trixie. :-] Best regards, -- Laurence 'GreenReaper' Parry

1 0

Blokir BNI Mobile banking
by payooy42＠gmail.com 14 Feb '26

14 Feb '26