Message of the day:
Security release 4.4.4 is out. Changelog: https://github.com/silverstripe/silverstripe-framework/blob/4/docs/en/04_Changelogs/4.4.4.md
SilverStripe 4 related information and questions.
@rista thank you kind Sir!
What about the injector causes it to throw a
Cannot declare class Vendor\\App\\Security\\MyAuthenticationHandler, because the name is already in use error?
- Name: mycoreauthentication
- - '#coreauthentication'
- class: Vendor\App\Security\MyAuthenticationHandler
Cool, thanks guys. Good to keep in the back of my mind 🙂
It wouldn’t make sense not to be able to do something from the web or the CLI respectively if they were different as not everyone has CLI access.
Ill delete my message just in case someone reads it
it was when webserver and cli were run under different user as the user is what differentiates the caches… if you run it under the same system user, the cache is just one
I’m afraid the separate cache manifests is not a thing in the above described way