Before including carrierwave-serializable gem in my Gem and installing it, my rails test passes.

After I include carrierwave-serializable gem in my Gem file then do a bundle install and lastly, a rails test, I get 8 test failures.

I did not even modify any other source file. How can my tests break all of a sudden?

Does carrierwave-serializable do some magic behind the scenes right after installing the gem with bundle install ?

I am worried it might conflict with some of my file naming or class naming.

I wrote a Stackoverflow question here: http://stackoverflow.com/questions/40890774/rails-installing-carrierwave-serializable-gem-causes-test-to-fail

I am using Active Model Serializer, Pundit, Knock and Carrierwave and Carrierwave Serializable gems.

My system is running Rails 5.0.0.1 and Ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]

Some times, I will import some image data from rake task, so, my mounted image
field will have a http://some_site/some_image.png value.

so,I will handle this situation with override uploader url method like this:

  def url
     # here, if not use a serialize field, model[mounted_as] will get the original value.
    original_url = model[mounted_as]

    original_url =~ %r{\Ahttps?://} ? original_url : super
  end

But if use serialize, model[mounted_as] or model.read_attribute[mounted_as is
not worked anymore,we need a new api to get the correct value.

currently, I have to do like this:

  def url
    serialize_to = model.class.serialized_uploaders[mounted_as]
    original_url = model[serialize_to][mounted_as.to_s]

    original_url =~ %r{\Ahttps?://} ? original_url : super

  end

Here, if can expose a original_url API, is good. Thanks.

# schema.rb
    t.jsonb    "delivery_info",         default: {}

  # order.rb

  # add return_logistics_image accessor method.
  store_accessor :delivery_info, :return_logistics_image
  mount_uploader :return_logistics_image, ImageUploader, serialize_to: :delivery_info

When create a new order object, exist following error:

NoMethodError (undefined method `return_logistics_image_changed?' for #<Order:0x007f1af7c68338>):
  app/models/order_transition.rb:7:in `block in <class:OrderTransition>'
  app/models/order.rb:182:in `transition_to!'
  app/models/order/buyer_action.rb:10:in `accept'
  app/models/concerns/set_order_action_callback.rb:13:in `public_send'
  app/models/concerns/set_order_action_callback.rb:13:in `block (2 levels) in method_added'
  app/models/concerns/set_order_action_callback.rb:12:in `block in method_added'
  app/api/api/buyer_action.rb:26:in `accept'
  app/controllers/orders_controller.rb:33:in `action!'
  app/controllers/buyer_orders_controller.rb:131:in `action!'

Hi everyone! Just me asking about an error.
I already properly install Carrierwave with multiple uploads, and now just trying to add serializable functionality for all those images.

My question is how should i define the hash in the whitelist parameters to accept a Hash variable.

Im getting the error: Attribute was supposed to be a Hash, but was a Array. -- []

The only place an array may appear (i think) its here:

def used_car_params
params.require(:used_car).permit(........, {pictures: []},
...
end

At least that works with simple multi uploads.

PD: Already did everything as explain before to configure, but looks like i miss something.
Thanks in advance.

Either this functionality should be added, or the documentation should be changed to reflect the fact that you can only use fields serialized to a hash.

This is because of this line:
https://github.com/timsly/carrierwave-serializable/blob/master/lib/carrierwave-serializable/orm/activerecord.rb#L66