Fatal declaration error due to monolog change about cloudinary_php HOT 3 CLOSED

Hi @const-cloudinary, yes adding "psr/log": "^1" to composer.json downgrades psr/log from 3.0.0 to 1.1.4 and that fixes the issue. I'm on PHP 8.0.10. Here is some code to reproduce:

$cloudAdmin = new Cloudinary\Api\Admin\AdminApi($config->cloudinaryUrl);
$result = (array) $cloudAdmin->asset($name);

from cloudinary_php.

@n8d , thanks for reporting the issue!

I couldn't reproduce the issue on my side using PHP 8.0.

What I did find is that monolog 2.3.4 requires psr/log: ^1.0.1 || ^2.0 || ^3.0
While monolog 2.3.3 requires psr/log: ^1.0.1 || ^2.0 which is not such a great difference.

They both should work with psr/log version 1.1.4.

I checked my composer.lock file, and it uses psr/log 1.1.4.

The issue with the newer psr/log versions is that they are only compatible with PHP 8 and up, while our library is compatible with the older versions of PHP.

Try setting psr/log: ^1 and check if it works for you with the latest version of monolog.

from cloudinary_php.

Hi there
I got the same issue after upgrading to cloudinary 2.4.0 on PHP 8.0.11. Limiting psr/log to ^1 worked for me as well. Thanks for the hint to fix this.
Wouldn't it make sense to limit psr to ^1 or ^2 in the cloudinary composer file the prevent this issue? I can imagine the there will be a lot of other users that will have the same issue after upgrading.

from cloudinary_php.