Closed m-vo closed 7 years ago
This might probably rather be a symfony problem than a contao issue as it happens in the assets:install --symlink --relative
command.
is the target an existing symlink or an actual folder?
An existing symlink.
I now ran vendor/bin/contao-console assets:install --symlink --relative
lots of times in a row.
Findings:
Is there a way to get more verbose output on the error?
Is there a way to get more verbose output on the error?
Yes, with -v
, -vv
and -vvv
;)
This never appeared again. I am therefore closing it.
When
ScriptHandler::initializeApplication()
gets executed during a composer operation, I've come across this problem (had it two or three times before but unfortunately don't know by what it's caused):(Output is from a console under windows - so that's why there are absolute symlinks and the warnings are as expected.)
One of the symlinks cannot be created. I don't know why composer tries to create the symlink in the first place as it is already existing and I don't know why the problem only happens for one of the packages.