The current composer configuration always installs the latest cloudinary/cloudinary_php, which is 1.8.0 and is not fully compatible. E.g. the files will be stored with a double file extension.
This problem was solved
The direct usage of paths as public ids was replaced
To prevent such future problems, the required version of cloudinary/cloudinary_php was changed to ^1.8.0
The current composer configuration always installs the latest
cloudinary/cloudinary_php, which is 1.8.0 and is not fully compatible. E.g. the files will be stored with a double file extension.cloudinary/cloudinary_phpwas changed to^1.8.0Similar approach to https://github.com/enl/flysystem-cloudinary/pull/10