We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried to start psym on a local symfony project, which has a dependency on imagick. However when I start psym I get the following error:
Imagine\Exception\NotSupportedException^ {#1626 #message: "Imagick driver not installed" #code: 0 #file: "./vendor/imagine/imagine/src/Imagick/DriverInfo.php" #line: 38 trace: { ./vendor/imagine/imagine/src/Imagick/DriverInfo.php:38 { …} ./vendor/imagine/imagine/src/Imagick/DriverInfo.php:68 { …} ./vendor/imagine/imagine/src/Imagick/Imagine.php:52 { …} ./vendor/imagine/imagine/src/Imagick/Imagine.php:41 { …} ./var/cache/dev/ContainerQA6qkmU/getLiipImagine_ImagickService.php:30
I have imagick installed but not loaded in global php.ini, rather in the project's folder php.ini which is used when I run symfony console commands:
symfony console
extension=amqp.so extension=imagick.so
It seems that psym does not read this file tho, leading to the error above. Thanks.
The text was updated successfully, but these errors were encountered:
Are you able to run bin/console?
bin/console
Sorry, something went wrong.
Yes I am able, but I get an error at the end of the output: Imagick driver not installed. I usually run symfony console tho.
Imagick driver not installed
No branches or pull requests
I tried to start psym on a local symfony project, which has a dependency on imagick. However when I start psym I get the following error:
I have imagick installed but not loaded in global php.ini, rather in the project's folder php.ini which is used when I run
symfony console
commands:It seems that psym does not read this file tho, leading to the error above.
Thanks.
The text was updated successfully, but these errors were encountered: