Failed to load file [2019-09/CF_128x128_1], [Resource not found - 2019-09/CF_128x128_1].
Failed to get sub-folders under folder [2019-09/CF_128x128_1], [Can't find folder with path 2019-09/CF_128x128_1].
InvalidArgumentException: The URI '' is invalid. You must use a valid URI scheme. in Drupal\Core\Url::fromUri() (line 281 of D:\xampp\htdocs\drupal8local\web\core\lib\Drupal\Core\Url.php).
I am seeing above errors in Log Messages, when I upload the Image to cloudinary
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | Fix-URI-not-found-3078828-15.patch | 1.13 KB | impol |
| #5 | Screen Shot 2019-10-02 at 3.23.05 PM.png | 319.05 KB | jlongbottom |
Comments
Comment #2
estrejlau commentedI'm seeing this as well, and need to add that the image is uploaded to Cloudinary, but does not show up in the database as having been associated with the node or entity on the given field.
Comment #3
naveenvalechaSeems like this is a duplicate of #3016606: Cannot upload image to cloudinary
Edit: Sam pointed that this is not a duplicate. So reopening it
Comment #4
naveenvalechaComment #5
jlongbottom commentedThis module is broken and totally unusable due to this issue. Not sure what is unique about my system that is causing the issue, because I find it hard to believe they cut this alpha release without testing it. Seems related to subfolders.
Uploading a single image results in all these errors in the logs:
Comment #6
jlongbottom commentedThe issue looks to be related to the AJAX behaviour of the Image widget on the field. It fails when trying to render the thumbnail after auto-uploading. If I disable AJAX on the field and submit the form the old-fashioned way, it seems to work for me.
Comment #7
jlongbottom commentedThe Image field widget auto-uploads on file selection and then generates a thumbnail and link. It is the link generation that causes the exception.
Commenting out this line in
file.modulefixes it for me, but its not a real or permanent solution.Comment #8
briangonzalezmiaI get the same error and the workaround in #7 still throws the same errors plus `This value should be of the correct primitive type.` That blocks saving the node. Any other ideas to fix the stream??
Comment #9
dorficus commentedThis is also broken on 8.8.0-alpha1. I am able to get the file to upload, but on the Drupal side there are issues and the media entity does not save as an entity.
I get the same laundry list of errors as in #5, but when i visit cloudinary the image is there waiting for me. I'll try to spend some time debugging this and see if I can get a patch together, but I don't know how much time I have to dedicate to this today.
Comment #10
hizbul25 commentedI am suffering with the same issue. I followed #7 process and the found the issue as #8. Anybody found any workaround?
Comment #11
impol commentedThe issue is reproducing when you have wrong cloudinary credentials or file in cloudinary already deleted, but exists in some field.
Here is a patch, which forces to output URL to file.
Comment #12
impol commentedAlso you must enable 'auto create directories' option under Cloudinary account, maybe it will help to resolve
Comment #13
impol commentedFix namespace
Comment #14
impol commentedNew fix
Comment #15
impol commentedFixed namespace
Comment #16
er11 commentedThis fix doesn't work
This bug needs to be re-opened
Comment #17
naveenvalechaComment #18
damondt commentedThis error can also happen due to this issue: https://www.drupal.org/project/cloudinary/issues/3171412