Cloudinary folder option not saving images to expected location
See original GitHub issueI have set the “Auto-create folders” for my Cloudinary account to true, but no matter what folder option I specify, or if I create the folder ahead of time at Cloudinary, images are always uploaded to the Cloudinary root.
Example model:
Sample.add({
title: { type: Types.Text, required: true, initial: true },
thumbnailImage: { type: Types.CloudinaryImage, folder: 'samples', autoCleanup: true },
});
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
node.js - Specifying "folder" option does not upload image to ...
The image uploads successfully, but always goes to the root of my media library. I have "auto create folders" enabled in my account...
Read more >Optimize Images | Cloudinary
Learn how to deliver optimized images with the smallest possible file size while maintaining visual quality, for improved page load times ...
Read more >Correct way of uploading from buffer? - Cloudinary Support
I have been researching for hours and I found out two solutions (using NodeJs), so that I can pass a buffer instead of...
Read more >Programmatically Uploading Images, Videos, and Other Files
For details, check the Account tab in your Cloudinary Console Settings. While you can use the REST API directly within your custom code...
Read more >Upload Widget - Cloudinary
<button id="upload_widget" class="cloudinary-button">Upload ... and the folder option, which uploads all images from the widget to a ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh absolutely. I have two sites currently in development for personal clients using Keystone.
One uses it as a full-stack solution for a public site plus as an API for an Aurelia powered SPA that is primarily designed for mobile.
The other site is full-stack. Additionally, Keystone powers my personal site as an API to an Aurelia front-end.
The dynamic admin is worth its weight in gold.
It’s been a busy year 😃