Page MenuHomePhabricator

[Task] extensions may not use class_exists to check if an extension is loaded
Closed, InvalidPublic

Description

Extensions need to not use class_exists to check if an extension is loaded, at least for extension classes that can be autoloaded without the extension being enabled. This might happen for extensions that have an composer generated autoloader and are handled by the composer merge plugin.
A replacement might be ExtensionRegistry->isLoaded('name') if the extension was converted to use that.

Related Objects

StatusAssignedTask
ResolvedAddshore
ResolvedAddshore
InvalidNone
DeclinedNone
InvalidNone
InvalidNone
OpenNone
ResolvedVictorbarbu
ResolvedLucas_Werkmeister_WMDE
ResolvedMtDu
ResolvedLydia_Pintscher
DeclinedLydia_Pintscher
InvalidNone
InvalidNone
ResolvedReedy
ResolvedLegoktm

Event Timeline

JanZerebecki raised the priority of this task from to Normal.
JanZerebecki updated the task description. (Show Details)
JanZerebecki added a project: Wikidata.
JanZerebecki added subscribers: JanZerebecki, Aklapper.
JanZerebecki renamed this task from extensions may not use class_exists to check if an extension is loaded to [Task] extensions may not use class_exists to check if an extension is loaded.Sep 10 2015, 8:45 PM
JanZerebecki moved this task from incoming to ready to go on the Wikidata board.
JanZerebecki set Security to None.
thiemowmde closed this task as Invalid.Sep 19 2017, 9:42 AM
thiemowmde added a subscriber: thiemowmde.

I'm going to close this ticket because it is – as it is now – not actionable. What this needs at least is a list of the specific extensions that need an update. What this tickets description suggests might still be done, but can be done any time with new, more specific tickets.

Restricted Application removed a subscriber: Liuxinyu970226. · View Herald TranscriptSep 19 2017, 9:42 AM