Closed therobyouknow closed 8 years ago
Solution appears to be:
sudo composer self-update
based on my research finding similar (but not exactly the same) error "Could not scan for classes inside"...
Reference (found by my research):
I then did:
composer install --prefer-dist
The --prefer-dist was because of a time out issue (perhaps not related to the original issue)
Reference:
The install proceeds past the place where it halted before and looks like it completed.
As this is the 1st mach on google, I'm posting this here:
I solved it by removing the core directory with rm -rf core
and running composer install
again
As this is the 1st mach on google, I'm posting this here: I solved it by removing the core directory with
rm -rf core
and runningcomposer install
again
Yes! You have to remove the entire "core" directory, not just the files in it.
Could you advise on how to resolve the error above, please? Thank you. My terminal log: