Issue with using multiple uploaders for a single model #743

Closed
rmatesic opened this Issue May 22, 2012 · 4 comments

Comments

Projects
None yet
4 participants
@rmatesic

Hi,

I have had an issue with carrierwave when using multiple uploaders in a single model and when it comes to returning that model as a json object.

I have a stack overflow question which explains the problem i had and how i fixed it. Not sure if this is a bug or not. But if you could take a look, it would be helpful thanks.

http://stackoverflow.com/questions/10594802/multiple-carrierwave-mount-uploader-on-a-single-model

@bensie

This comment has been minimized.

Show comment Hide comment
@bensie

bensie May 31, 2012

Owner

While I have not had time to fully investigate, I can confirm that this is a bug.

Owner

bensie commented May 31, 2012

While I have not had time to fully investigate, I can confirm that this is a bug.

@bensie

This comment has been minimized.

Show comment Hide comment
@bensie

bensie May 31, 2012

Owner

I've added a spec for this issue but could not reproduce your issue. If possible, please send a failing spec or a sample app demonstrating this behavior. Are you using the latest version of CarrierWave?

Owner

bensie commented May 31, 2012

I've added a spec for this issue but could not reproduce your issue. If possible, please send a failing spec or a sample app demonstrating this behavior. Are you using the latest version of CarrierWave?

@bensie bensie closed this May 31, 2012

@jgorset

This comment has been minimized.

Show comment Hide comment
@jgorset

jgorset Jun 6, 2012

We're seeing this behavior in our application as well. I'll try to get around to send you a sample application.

jgorset commented Jun 6, 2012

We're seeing this behavior in our application as well. I'll try to get around to send you a sample application.

@nvdk

This comment has been minimized.

Show comment Hide comment
@nvdk

nvdk Sep 18, 2012

We too are seeing this behaviour in our application, we are using carrierwave in combination with mongoid (version 3.0.5) and the mongoid-3 branch of your carrierwave-mongoid gem.

nvdk commented Sep 18, 2012

We too are seeing this behaviour in our application, we are using carrierwave in combination with mongoid (version 3.0.5) and the mongoid-3 branch of your carrierwave-mongoid gem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment