Open sandric opened 6 years ago
Any ideas?
Hi @sandric. We've identified the issue - version
remains nil
after the update instead of been populated with the new version.
We'll update as soon as we'll have an ETA for a fix.
Any progress on this? I guess there should be fairly simple in-place fix untill pr with real fix is merged maybe?
Hi @sandric, no ETA yet as we're still reviewing the issue and possible solutions. We'll update on any progress done.
Hi, I having strange issue that I found many people struggle with through out issues, but I havent found how to make it using carrierwave. My problem is that if I have cloudinary carrierwave uploader on field in model and currently that field is nil and I upload new image using just simple_form form submit - it appears in cloudinary dashboard and as actual field in model so I can see uploaded image on site. Issue occurs when I want to update existing image on model - after
model.update_attributes
call with saylogo
parameter from form submitted, I see new image occurs in dashboard and old one is gone, however, my model still having old image in its field, so that I see only old image on site.For example, my model
Comany
is Neo4j one, and in it is only that:CompanyLogoUploader
:Now, if I have company model without logo and upload new one, all is great and here what I see as logo:
It appears in dashboard with url: "https://res.cloudinary.com/davsupw1h/image/upload/v1532952671/spikbsjvpx9tkgi78c3w.jpg"
Now, If I'll change this image to smth else, here's updated debug:
Whereas new image that got updated in dashboard has url "https://res.cloudinary.com/davsupw1h/image/upload/v1532953062/spikbsjvpx9tkgi78c3w.jpg" - version is changed.
So my question is next - should I pass version somehow in image uploader, and how/where? If yes then why does carrierwave integration by default does not using version and rely on caching? Can I turn it off somehow, in uploader, in cloudinary initializer? Thanks.