Jump to content

Topic on Project:Support desk/Flow

PHP Deprecated:  (Extension name)'s extension.json or skin.json does not have manifest_version

5
Summary by Jonathan3

Added "manifest_version": 2

Jonathan3 (talkcontribs)

I've noticed this deprecation notice on some extensions of mine I've cobbled together over the years

Over half the extensions I have from mediawiki.org have <code>"manifest_version": 2</code> and the rest have <code>"manifest_version": 1</code>.

I can see from Manual:Extension.json/Schema#manifest version that these are the two choices, but can't work out much more than that.

Which should I use?

Jonathan3 (talkcontribs)

I've gone for "1" in the meantime!

Samwilson (talkcontribs)

@Jonathan3: I think you'd be best off moving to version 2, and fixing any issues that arise. It's the way of the future after all! :-P

Jonathan3 (talkcontribs)

Cool. Done. In one of the extensions that caused (with ExtensionName replacing the actual name):

  • PHP Warning: array_key_exists() expects parameter 2 to be array, bool given in /var/www/html/includes/registration/ExtensionProcessor.php on line 830
  • PHP Fatal error: Uncaught UnexpectedValueException: Missing value for config ExtensionNameEnableFoo in /var/www/html/includes/registration/ExtensionProcessor.php:831 for a "config" value. It was just a leftover from whatever example template I'd based it on, so getting rid of it solved things.

For my own future reference, this is what caused the problem:

	"config": {
		"ExtensionNameEnableFoo": true
	},
Jonathan3 (talkcontribs)