February 2026 - Wikibase Community User Group

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