Page MenuHomePhabricator

entityNamespaces wikibase-item setting conflict on commonswiki
Closed, ResolvedPublic

Description

WikibaseClient now needs to know the entityNamespaces setting for it's repo (e.g. Wikidata).

For commons, that means to set:

$wgWBClientSettings['entityNamespaces']['wikibase-item'] = NS_MAIN;

When we enable MediaInfo, then commons will also become a repo and obviously can't have items in the main namespace. (and maybe won't have items at all?)

so we need to unset the above (and then some client stuff breaks?) or make it explicit it's for client only.

Event Timeline

Change 446843 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[operations/mediawiki-config@master] Install but don't enable the WikibaseMediaInfo extension, part III

https://gerrit.wikimedia.org/r/446843

Change 446843 merged by jenkins-bot:
[operations/mediawiki-config@master] Install but don't enable the WikibaseMediaInfo extension, part III

https://gerrit.wikimedia.org/r/446843

Jdforrester-WMF subscribed.

Still a problem, I think; we've just hacked past it for now?

I believe I fixed this with all of the re organizing that I did in mediawiki-config pre commons deployment

But now with the commons deployment things look to be in an odd state?

'wmgWikibaseRepoEntityNamespaces' => [
	'default' => [],
	'wikidata' => [
		'item' => 0,
		'property' => 120,
		'lexeme' => 146,
	],
	'testcommonswiki' => [],
],

Not sure why mediainfo isn't listed there? Or what consequences this has without a deeper dive.

I believe I fixed this with all of the re organizing that I did in mediawiki-config pre commons deployment

But now with the commons deployment things look to be in an odd state?

'wmgWikibaseRepoEntityNamespaces' => [
	'default' => [],
	'wikidata' => [
		'item' => 0,
		'property' => 120,
		'lexeme' => 146,
	],
	'testcommonswiki' => [],
],

Not sure why mediainfo isn't listed there? Or what consequences this has without a deeper dive.

Sorry, I just need to clean that up; testcommonswiki can be removed, it's a no-op now.