Old image kept on cloudinary

Open
#311 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rails, ruby
Domain
backend, cloud

Research direction

Start by reproducing an image update through a Rails form using update_attributes and the CarrierWave uploader, then trace how the Cloudinary asset is replaced. Check whether the uploader exposes deletion or replacement behavior; done means updating an image leaves only the intended current asset on Cloudinary.

Written by the indexing model from the issue text.

Description

bug

Hi,
When I'm updating image from rails form, through update_attributes and carrierwave uploader, on cloudinary both: new and old images are kept. Is it possible to override this behavior?
Thanks in advance.

Dominant language
Ruby
Stars
420
Forks
282
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudinary/cloudinary_gem

All issues in cloudinary/cloudinary_gem

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.