Closed adriankirchner closed 5 years ago
Yep, this is "breaking" our Oxid Backends currently, too :( Can't use the module management because of this exception ...
workaround for this is to install the oxid console
composer require oxid-professional-services/oxid-console
Yes, I know, but we already use oxrun :) We are downgrading / pinning to 1.0.x for now, at least for auto-deployed shops
status: seams to have a wrong use statement in https://github.com/OXIDprojects/oxid-module-internals/blob/master/Core/ModuleStateFixer.php#L13
https://github.com/OXIDprojects/oxid-module-internals/blob/3ef518018b36f7b4944dbca7e8202ed5ef19afdb/Core/ModuleStateFixer.php#L23
This dependency to oxid-console should get either removed or registered via composer. An a fresh CE 6.1.1 this results in: