# Rails 2.3.2 upgrade to 2.3.8 problem

**URL:** <https://www.ruby-forum.com/t/rails-2-3-2-upgrade-to-2-3-8-problem/190624>\
**Category:** Rails\
**Created:** [June 24, 2010, 4:09am UTC](https://www.ruby-forum.com/t/rails-2-3-2-upgrade-to-2-3-8-problem/190624 "2010-06-24T04:09:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bruparel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/e47774/32.png) [@bruparel](https://www.ruby-forum.com/u/bruparel)\
**Post date:** [June 24, 2010, 4:09am UTC](https://www.ruby-forum.com/t/rails-2-3-2-upgrade-to-2-3-8-problem/190624/1 "2010-06-24T04:09:48Z")

</div>

Upgrading to Rails 2.3.8 from 2.3.2 has broken views in my application.  
Specifically the field labels are all displaying after the label  
text and therefore the alignment is all messed up. Instead of nicely  
aligning with the label text on the top and text entry field under it,  
they line up side-by-side and are misaligned. The tell-tale sign is the  
appearance of tag after the label text.  
Is there something in Rails 2.3.8 changed. All i did was I changed the  
Rails version in the environment.rb file from 2.3.2 to 2.3.8 and kept  
everything the same.  
Please help.  
Thanks.  
Bharat

---

<div class="post-metadata">

**Author:** ![bruparel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/e47774/32.png) [@bruparel](https://www.ruby-forum.com/u/bruparel)\
**Post date:** [June 24, 2010, 5:14am UTC](https://www.ruby-forum.com/t/rails-2-3-2-upgrade-to-2-3-8-problem/190624/2 "2010-06-24T05:14:18Z")

</div>

Quoting Bharat R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):

> Upgrading to Rails 2.3.8 from 2.3.2 has broken views in my application.  
> [snip]

Rails 2.3.8 is a stepping stone to Rails 3 with lots of deprecation  
warnings  
and some actual changes. And not all Gems and plugins are compatible  
with  
it. I suggest migrating from 2.3.2 to 2.3.5 first. Then try going to  
2.3.8.  
And expect problems in both your code and others’ code. I.e., allocate  
time  
to do the conversion and accept that you may have to wait for compatible  
gems/plugins to be available. (Or figure the necessary patches and  
submit  
them to the author.)

HTH,  
Jeffrey