Keystone-classic: Cloudinary folder option not saving images to expected location

[alsoicode]

I 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 },
});

[njk]

did you set 'cloudinary folders': true in keystone? @alsoicode

[mxstbr]

What @njk said should solve your problem as far as I understand, so I'll close this issue for now. Feel free to comment again if this is still an issue for you!

[alsoicode]

Sorry for the _extremely_ late reply, but I can confirm that adding the cloudinary folders setting is working as expected.

[mxstbr]

Hah, awesome that you came back! Glad to hear!

[alsoicode]

It's been a busy year :)

[mxstbr]

That's the way it should be! Still using Keystone?

[alsoicode]

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.

[mxstbr]

So happy to hear that, you're going to _love_ 0.4 when we finally release it! Rock on!