Closed marekgach closed 5 years ago
I have optimize-autoloader
set to true in my composer.json
. This is the only part that possibly can cause such an issue when the directory structure is not according to PSR-4 rules.
So what I found out after a few hours is that the machine was running an older Composer. But still not any super very old one:
Composer version 1.2.1 2016-09-12 11:27:19
So the issue was fixed after the Composer upgrade. However, I think this may be a good idea you will change the directory structure to comply with PSR-4. Because only this error is blocking it from running in older Composer
. I can approve in Composer 1.6
everything is working fine.
Decide what to do, comment and feel free to close this issue. Thanks!
hey @marekgach. You are absolutely right - thanks to composer, this issue never showed up! I'll fix it right away.
Installed libraries:
After a fresh install of those version combinations, I am not able to run any command from Pimcore console.
After running
php bin/console cache:clear --no-warmup
or evenphp bin/console
the command seems to run but new error is emmited tovar/logs/php.log
:When I was doing some investigation it seems there is some problem with an autoloader. Class
UserAwareEncoderFactory
is in namespaceMembersBundle\Security\Encoder\Factory
however directory structure is missing last part and isMembersBundle\Security\Encoder
which will make mess in PSR-4 autoloading.When I did some small test and moved class in my
vendor
folder into the correct place everything started to work:Maybe some autoloader generation or some special config breaks it up, but I am not aware of anything like this. At least I personally think the directory structure will not work with PSR-4.
Waiting for your comments. Maybe I miss something heavily.