5 ms·

> Many of the gems/plugins which you might be using with your current application will not be compatible with Rails 3. I'm genuinely curious what gems people a

> Many of the gems/plugins which you might be using with your current application will not be compatible with Rails 3. I'm genuinely curious what gems people are using that are not yet compatible with Rails 3, given that it was released almost three years ago. Maybe my use cases for Rails don't match the most common ones, but I have yet to run into this issue. For Rails 4, well, that's another matter =)

steveklabnik 13y ago
I am interested in helping gems that are not Rails 4 compatible get so, so if you can point me towards some that aren't, I'll reach out to the maintainers.
- Aqua_Geek 13y ago
  Thanks! MongoMapper is at the top of my list. Hard dependency on ActiveModel 3.
  - steveklabnik 13y ago
    Cool, I'll get in touch with them. EDIT: Here's the status: https://github.com/jnunemaker/mongomapper/issues/493 https://github.com/jnunemaker/mongomapper/issues/493
- tomfakes 13y ago
  Active Admin is getting there in a branch, but I do like to have rubygems.org gems for production apps. I've just started using the Turkee gem, and this needs the mass-assignment gem with Rails 4 to work correctly. Since I'm new to this one, I need to spend more time with it before I can send in some pull requests to provide patches
  - steveklabnik 13y ago
    I hear you about the branch issue. Thanks!
- ilikepi 13y ago
  We're tracking Rails 4 compatibility for the major gems we use, based on a bit of skimming GitHub Issues and Pull Requests. Here are the highlights from that list: CanCan[1] has a '2.0' branch where Rails 4 support is being worked on. It also has PR #838 open for supporting strong_parameters in the current stable 1.6 tree. Devise[2] pushed 3.0.0.rc about a month ago with Rails 4 support. FriendlyId[3] seems to have work in progress on their master branch. Acts-as-taggable-on[4] states in their README that they are compatible in version 2.4.1, but there seem to be a couple open issues related to Rails 4. edit: formatting [1]: https://github.com/ryanb/cancan/ https://github.com/ryanb/cancan/ [2]: https://github.com/plataformatec/devise/ https://github.com/plataformatec/devise/ [3]: https://github.com/FriendlyId/friendly_id https://github.com/FriendlyId/friendly_id [4]: https://github.com/mbleigh/acts-as-taggable-on https://github.com/mbleigh/acts-as-taggable-on
  - steveklabnik 13y ago
    Great! I am using CanCan 1.6.7 with Rails 4, and I haven't hit anything yet. Even using strong params.
  - voltagex_ 13y ago
    I mean this in a friendly way, but it's nice to see that it's not just Python that has issues with major version bumps.
- boboroshi 13y ago
  Compass Rails could use some help: https://github.com/Compass/compass-rails https://github.com/Compass/compass-rails There's also some issues with Ruby 2.0 support in it and in Compass itself, if memory serves...
- skateinmars 13y ago
  I'm late to the party but we have a list of some outdated gems that are still not compatible with Rails 4 (we use a long-lived branch for rails 4 compatibility that should be merged once rails 4 is released and all our dependencies are compatible). * client_side_validations : There is an outdated rails 4 branch * client_side_validations-simple_form : this is trickier because it also needs compatibility with the next simple_form major version. AFAIK no work is done at the moment * active_enum : looks like simply updating the gemspec may be enough * ransack : there is an outdated rails-4 branch, I'm not sure what the current compatibility status is Other than that a few gems have still not released stable versions with rails 4 compatibility and only have support in a RC or even just their master branch (for instance: simple_form, database_cleaner, sass-rails)
caw 13y ago
I helped my friend upgrade a 2.x app to 3.x about a year ago, and attachment_fu wasn't compatible. The Internet seemed to be pointing to other alternatives but they required database schema migrations (no drop-in replacements).
- steveklabnik 13y ago
  Isn't Paperclip a drop-in? Maybe not any more, but when it first came out, it was...
  - caw 13y ago
    I don't remember exactly, it was a while ago. I was looking at this SO thread: http://stackoverflow.com/questions/4445244/attachment-fu-or-paperclip-for-rails3 http://stackoverflow.com/questions/4445244/attachment-fu-or-....
  - gugachiu 13y ago
    Paperclip has a small migration requirement where they add metadata(file_name, content_type,etc...) about the file to the related table.

steveklabnik 13y ago

I am interested in helping gems that are not Rails 4 compatible get so, so if you can point me towards some that aren't, I'll reach out to the maintainers.

Aqua_Geek 13y ago
Thanks! MongoMapper is at the top of my list. Hard dependency on ActiveModel 3.
- steveklabnik 13y ago
  Cool, I'll get in touch with them. EDIT: Here's the status: https://github.com/jnunemaker/mongomapper/issues/493 https://github.com/jnunemaker/mongomapper/issues/493
tomfakes 13y ago
Active Admin is getting there in a branch, but I do like to have rubygems.org gems for production apps. I've just started using the Turkee gem, and this needs the mass-assignment gem with Rails 4 to work correctly. Since I'm new to this one, I need to spend more time with it before I can send in some pull requests to provide patches
- steveklabnik 13y ago
  I hear you about the branch issue. Thanks!
ilikepi 13y ago
We're tracking Rails 4 compatibility for the major gems we use, based on a bit of skimming GitHub Issues and Pull Requests. Here are the highlights from that list: CanCan[1] has a '2.0' branch where Rails 4 support is being worked on. It also has PR #838 open for supporting strong_parameters in the current stable 1.6 tree. Devise[2] pushed 3.0.0.rc about a month ago with Rails 4 support. FriendlyId[3] seems to have work in progress on their master branch. Acts-as-taggable-on[4] states in their README that they are compatible in version 2.4.1, but there seem to be a couple open issues related to Rails 4. edit: formatting [1]: https://github.com/ryanb/cancan/ https://github.com/ryanb/cancan/ [2]: https://github.com/plataformatec/devise/ https://github.com/plataformatec/devise/ [3]: https://github.com/FriendlyId/friendly_id https://github.com/FriendlyId/friendly_id [4]: https://github.com/mbleigh/acts-as-taggable-on https://github.com/mbleigh/acts-as-taggable-on
- steveklabnik 13y ago
  Great! I am using CanCan 1.6.7 with Rails 4, and I haven't hit anything yet. Even using strong params.
- voltagex_ 13y ago
  I mean this in a friendly way, but it's nice to see that it's not just Python that has issues with major version bumps.
boboroshi 13y ago
Compass Rails could use some help: https://github.com/Compass/compass-rails https://github.com/Compass/compass-rails There's also some issues with Ruby 2.0 support in it and in Compass itself, if memory serves...
skateinmars 13y ago
I'm late to the party but we have a list of some outdated gems that are still not compatible with Rails 4 (we use a long-lived branch for rails 4 compatibility that should be merged once rails 4 is released and all our dependencies are compatible). * client_side_validations : There is an outdated rails 4 branch * client_side_validations-simple_form : this is trickier because it also needs compatibility with the next simple_form major version. AFAIK no work is done at the moment * active_enum : looks like simply updating the gemspec may be enough * ransack : there is an outdated rails-4 branch, I'm not sure what the current compatibility status is Other than that a few gems have still not released stable versions with rails 4 compatibility and only have support in a RC or even just their master branch (for instance: simple_form, database_cleaner, sass-rails)

caw 13y ago

I helped my friend upgrade a 2.x app to 3.x about a year ago, and attachment_fu wasn't compatible. The Internet seemed to be pointing to other alternatives but they required database schema migrations (no drop-in replacements).

steveklabnik 13y ago
Isn't Paperclip a drop-in? Maybe not any more, but when it first came out, it was...
- caw 13y ago
  I don't remember exactly, it was a while ago. I was looking at this SO thread: http://stackoverflow.com/questions/4445244/attachment-fu-or-paperclip-for-rails3 http://stackoverflow.com/questions/4445244/attachment-fu-or-....
- gugachiu 13y ago
  Paperclip has a small migration requirement where they add metadata(file_name, content_type,etc...) about the file to the related table.