Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

AssetManager could not be initialized #172

Open
Avatar4eg opened this issue Aug 1, 2016 · 6 comments
Open

AssetManager could not be initialized #172

Avatar4eg opened this issue Aug 1, 2016 · 6 comments

Comments

@Avatar4eg
Copy link

After clean installation:

  1. composer create-project -sdev zfcampus/zf-apigility-skeleton
  2. composer update
    I have an error:
    Zend\ModuleManager\Exception\RuntimeException: Module (AssetManager) could not be initialized. in C:\_work\projects\sites\site_dotaquiz\vendor\zendframework\zend-modulemanager\src\ModuleManager.php on line 203

Tried to install zfcampus/zf-asset-manager.

@michalbundyra
Copy link
Member

@Avatar4eg zfcampus/zf-apigility-skeleton is not yet updated to use ZF3 modules, please use zf-apigility v1.2

@Avatar4eg
Copy link
Author

I also use zfcampus/zf-apigility-doctrine, which has version conflicts if packages not updated.

@michalbundyra
Copy link
Member

@Avatar4eg Yes, I'm working on it, doctrine modules are not yet release to support ZF3 modules, need to be patient to use it will ZF3. I'd suggest to use it on ZF2 for now or wait few more days and start on ZF3.

@morrsky
Copy link

morrsky commented Aug 25, 2016

In my case what helped is composer require rwoverdijk/assetmanager

@michalbundyra
Copy link
Member

@jamjan It is possible now because rwoverdijk/assetmanager is finally updated to support ZF2 and ZF3. More about this change in apigility you can read here:
https://apigility.org/documentation/intro/updating-to-1-4#asset-management

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at laminas-api-tools/api-tools#21.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants