#108364Check for invalid or missing composer.json in Install Tool
Description
With #108310 the composer.json is also required for non-composer mode. As it might be confusing for ppl upgrading why their extensions are suddenly not working / not activatable I would suggest to test for a valid composer.json in “System > Upgrade > Check for broken extensions”
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 3
History 8
-
Lina Wolf changed Related to #108310 <span data-processor="relativetime" data-value="2025-11-30T05:33:09+00:00" > 11/30/25, 05:33 </span>
-
Lina Wolf commented <span data-processor="relativetime" data-value="2026-02-27T07:00:36+00:00" > 02/27/26, 07:00 </span>
So we already have the test then, so we could display the result in “Check for broken extensions”?
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2026-02-27T09:59:11+00:00" > 02/27/26, 09:59 </span>
-
Garvin Hicking changed Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2026-08-06T16:21:32+00:00" > 08/06/26, 16:21 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-10-31T14:36:33+00:00" > 10/31/26, 14:36 </span>With #109659 unlisting such extensions is logged, therefore closing the issue
-
Georg Ringer changed Related to #109659 <span data-processor="relativetime" data-value="2026-10-31T14:36:38+00:00" > 10/31/26, 14:36 </span>
-
Georg Ringer changed Related to #108365 <span data-processor="relativetime" data-value="2026-10-31T14:36:52+00:00" > 10/31/26, 14:36 </span>
are you aware that there is a check in extension manager for that and that it is also exposed to reports module?