Assetic version on composer.json about assetmanager HOT 10 CLOSED

I sort of agree that the version should be changed. However, I've never experienced any problems with the default setup for bootstrap. Try updating your assetmanager copy.

Sidenote, please don't use APC for assets. Pleeeeeaaaase.

from assetmanager.

Apc choosing was a blind one based on your SxBootstrap wiki, just following the manual. Since you've started, what's wrong with Apc? What do you recommend?

Regarding the version I tested with zf2 skeleton app, and even removed composer's cache folder, still getting the same version installed. Maybe if you clean composer's cache folder you'll be able to reproduce this. Anyways, not huge hassle, but SxBootstrap cache might suffer from this, since it won't find any of the Cache type class files from Assetic.

EDIT:
I guess I saw why you don't want Apc use ;) Using filesystem cache and working wonders (with the package fix).
Cheers

from assetmanager.

Well, that's odd. It should be finding the cache... I'll look into it when I have time, pinky promise ;)

I'm glad you figured that out. Serving assets through php is not a good idea, that's why I use the FilePathCache.

from assetmanager.

I too have to use "minimum-stability": "alpha" in order to use assetmanager. I've also tried adding @Alpha in a fork of this project, however it still required me to set the minimum stability to alpha in the project composer?

from assetmanager.

Hey. We're still looking into this issue. We're hoping that assetic will soon create a tag.

from assetmanager.

That would be preferable! I'll keep trying though and if I find anything useful I'll post it here.

from assetmanager.

Any news on when we won't require alpha stability?

from assetmanager.

Ping @stof - alpha4 of assetic is 2 months old - did the release process halt for some particular reason?

from assetmanager.

The latest version of assetic is 1.1.2. Can this issue be closed now?

from assetmanager.

@internalsystemerror It should, yes.

from assetmanager.