-
Notifications
You must be signed in to change notification settings - Fork 935
-
Notifications
You must be signed in to change notification settings - Fork 935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.0] Target [Anomaly\UsersModule\User\Contract\UserRepositoryInterface] is not instantiable. #3461
Comments
Revamping the installer literally right now. No worries ^_^ On Mar 18, 2015, at 6:34 AM, REMY Matthieu <notifications@github.commailto:notifications@github.com> wrote: I have this error with a fresh install : Target [Anomaly\UsersModule\User\Contract\UserRepositoryInterface] is not instantiable. Steps to reproduce : git clone https://github.com/pyrocms/pyrocms.git Then run the installer. Installer ends with error : — |
This should be long fixed by now ^_^ |
I use phpStorm to install pyrocms 3 and still meet this issue. How to fix it? |
What's your environment look like? |
I've got the same error using mamp pro with php 5.6.10, has all the extensions mentioned in the requirements. If you need any more details let me know. Beta 2 is working okay on that setup. |
Can you guys try deleting any compiled.php file in bootstrap/cache/ Also try composer dump-autoload |
Since using MAMP - does changing to PHP 7 work? Also disable opcache if you have it enabled. |
I am having the same problem. Just tried to set up a sandbox using Laravel Homestead (PHP7) with the current 3.0 master branch. |
@haeflimi can you paste the entire stack trace? |
I just realised it's not the exact same Error, but Google brought me streight here and it is similar :
|
Same as haeflimi Have made sure opcache is disabled, on an older version of MAMP without PHP 7, will upgrade and see if it makes a difference :-) |
Just tried with PHP7 on mamp, returns the same error. |
I think this is good now - can you check? |
Tried with a fresh install, sorry same error. |
I don't think so if it's new @j-hubb - pull users / core with git and yours should clear up |
Ignore me. This is related to another issue (I've posted there) |
Good for me now, cheers! |
@aidanwatt woot! |
@aidanwatt What did you do to get it working?
I thought i might do something wrong and started over agin. Also tried the develop branch. Same result. |
alright, just managed to resolve it. All looks good right now. |
Sorry yeah should have posted.. @RyanThompson had pushed some fixes and there was a discussion on the slack channel, I just ran an update with --no-scripts same as you. |
@haeflimi glad you got it working man - another good tip to know if you ever corrupt your file base or something (deleting / whatever) and need to re-composer install / update. You can mark INSTALLED=false in the .env file too and that will prevent Streams from looking for add ons. |
I have this error with a fresh install :
Steps to reproduce :
The text was updated successfully, but these errors were encountered: