jakx in #ss4 2019-09-06 07:02:05 (edited) (deleted)

What about the injector causes it to throw a Cannot declare class Vendor\\App\\Security\\MyAuthenticationHandler, because the name is already in use error?


  1. ---
  2. Name: mycoreauthentication
  3. After:
  4. - '#coreauthentication'
  5. ---
  6. SilverStripe\Core\Injector\Injector:
  7. SilverStripe\Security\AuthenticationHandler:
  8. class: Vendor\App\Security\MyAuthenticationHandler

Cool, thanks guys. Good to keep in the back of my mind 🙂


@jkersu the same things happen in the same way - except that as @MichalKleiner has said, it stores the info in an entirely separate place. It will however affect common components - generally the Database.


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.

Bjorn Bojumble

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