Look for alternative solution from updating rails gem to 2.3.12 from 2.3.5

Rails
1

Hello All,

I have updated my rubygems version to 1.8.5 for the purpose of i18n

gem but after this when i start my rails application which is in the
version 2.3.5 is throwing the following error:

gem_dependency.rb:268:in ==': undefined methodname’ for
“actionmailer”:String (NoMethodError)

Some developers are suggesting to update my rails version to 2.3.12 from
2.3.5(in which the app was running this long).

Is there any way to solve this issue avoiding the rails update and
keeping the rails version in 2.3.5 itself.

2

Hello All,
I have updated my rubygems version to 1.8.5 for the purpose of i18n
gem but after this when i start my rails application which is in the
version 2.3.5 is throwing the following error:

gem_dependency.rb:268:in ==': undefined methodname’ for
“actionmailer”:String (NoMethodError)

Some developers are suggesting to update my rails version to 2.3.12 from
2.3.5(in which the app was running this long).

Is there any way to solve this issue avoiding the rails update and
keeping the rails version in 2.3.5 itself.

Sure there is. All this stuff is open source. You could fork whatever
project is generating that error and fix it. Of course, that would most
likely be quite a bit more difficult than just upgrading to 2.3.12 and
moving forward.

Once you get to 2.3.12 start thinking about bringing your project
forward to Rails 3.1. Issues like this are only going to get worse over
time. There will be a diminishing effort to keep Rails 2.3.x working
with newer versions of Ruby, RubyGems and Gems in general.

3

Hi Robert,

Your reply is indeed making sense. I will take steps to reach rails

3.1.x.

Thanks.

Robert W. wrote in post #1008345:

Hello All,
I have updated my rubygems version to 1.8.5 for the purpose of i18n
gem but after this when i start my rails application which is in the
version 2.3.5 is throwing the following error:

gem_dependency.rb:268:in ==': undefined methodname’ for
“actionmailer”:String (NoMethodError)

Some developers are suggesting to update my rails version to 2.3.12 from
2.3.5(in which the app was running this long).

Is there any way to solve this issue avoiding the rails update and
keeping the rails version in 2.3.5 itself.

Sure there is. All this stuff is open source. You could fork whatever
project is generating that error and fix it. Of course, that would most
likely be quite a bit more difficult than just upgrading to 2.3.12 and
moving forward.

Once you get to 2.3.12 start thinking about bringing your project
forward to Rails 3.1. Issues like this are only going to get worse over
time. There will be a diminishing effort to keep Rails 2.3.x working
with newer versions of Ruby, RubyGems and Gems in general.