# Recent Upgrade to 2.1.0 not working IE7

**URL:** <https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130>\
**Category:** rubyonrails-talk\
**Created:** [October 7, 2008, 5:20pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130 "2008-10-07T17:20:14Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![11175](https://avatars.discourse-cdn.com/v4/letter/1/8edcca/32.png) [@11175](https://discuss.rubyonrails.org/u/11175)\
**Post date:** [October 7, 2008, 5:20pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/1 "2008-10-07T17:20:14Z")

</div>

I recently upgraded to Rails 2.1.0 and thought that everything worked - I work mostly in FireFox and Crome - but when I went to do testing in IE7, pretty much nothing works. I have my app broken down into about 10 seperate pages, all of which make use of auto\_complete, in\_place\_editors, and various rails helper (and I have added all the appropriate plugins), I also have some before\_filters in place for user authentication. Has anyone had problems after upgrading where IE7 starts throwing 500 errors, while every other browser works fine and how did you fix it? Thanks,

-S

---

<div class="post-metadata">

**Author:** ![Freddy\_Andersen](https://avatars.discourse-cdn.com/v4/letter/f/ecae2f/32.png) [@Freddy\_Andersen](https://discuss.rubyonrails.org/u/Freddy_Andersen)\
**Post date:** [October 7, 2008, 7:00pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/2 "2008-10-07T19:00:56Z")

</div>

IE throwing 500 errors?!

What do you have in your rails log? Could you post a stack trace for the 500 error you get.

Is this development or production env.

---

<div class="post-metadata">

**Author:** ![Craig\_Demyanovich](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@Craig\_Demyanovich](https://discuss.rubyonrails.org/u/Craig_Demyanovich)\
**Post date:** [October 8, 2008, 4:24am UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/3 "2008-10-08T04:24:49Z")

</div>

Some time ago, I had a problem on my project with error 500 when using IE 6/7. I think it was because I was doing $this instead of $(this) in some JavaScript. I don’t remember much more about the problem, though.

Regards, Craig

---

<div class="post-metadata">

**Author:** ![11175](https://avatars.discourse-cdn.com/v4/letter/1/8edcca/32.png) [@11175](https://discuss.rubyonrails.org/u/11175)\
**Post date:** [October 8, 2008, 12:37pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/4 "2008-10-08T12:37:46Z")

</div>

I'm not using $(this) anywehere, but what I did notice was that my project isn't holding any session variables, and since I make heavey use of those session variables I always get a use of a nil object error when I shouldn't. Has something changed in rails 2.1.0. in regards to session variables and how they are kept? Thanks,

-S

---

<div class="post-metadata">

**Author:** ![Craig\_Demyanovich](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@Craig\_Demyanovich](https://discuss.rubyonrails.org/u/Craig_Demyanovich)\
**Post date:** [October 8, 2008, 12:44pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/5 "2008-10-08T12:44:13Z")

</div>

Could you share a backtrace of one of the errors that you’re seeing?

Craig

---

<div class="post-metadata">

**Author:** ![11175](https://avatars.discourse-cdn.com/v4/letter/1/8edcca/32.png) [@11175](https://discuss.rubyonrails.org/u/11175)\
**Post date:** [October 8, 2008, 1:30pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/6 "2008-10-08T13:30:12Z")

</div>

This is the error I get:

Called id for nil, which would mistakenly be 4 -- if you really wanted the id of nil, use object\_id

app/controllers/enroll\_controller.rb:125:in `check_authentication' -e:4:in `load' -e:4

I know what it means but the thing is is that it shouldn't be erroring out. It is erroring out because it doesn't like this:

if @user.id != session[:user].id

It thinks that session[:user] is nil and it is, but the thing is is that it shouldn't be. The check\_authentication checks to see if a user that is logged in is who they say they are. When they login the first thing that happens is that a session gets started - session[:user] - then they get redirected to the appropriate pages and the check\_authentication method gets called. I can see the session variable getting set but then as we move further along in the process it disapears? And when I look in my session folder under tmp it is empty which leads me to beleive that, for whatever reason, the sessions are getting created just like they should and then immediatly destroyed.

This is wasn't a problem a week ago, but last week I upgraded to rails 2.1.0. from 1.2.? and then this started happening. So I am kinda at a loss as to what is happening and how to fix it. Thanks,

-S

---

<div class="post-metadata">

**Author:** ![Craig\_Demyanovich](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@Craig\_Demyanovich](https://discuss.rubyonrails.org/u/Craig_Demyanovich)\
**Post date:** [October 8, 2008, 2:29pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/7 "2008-10-08T14:29:23Z")

</div>

Out of curiosity, do you have a config.action\_controller.session entry in config/environment.rb? It should look something like:

config.action\_controller.session = { :session\_key =\> ‘\_\<your\_app\_name\>\_session’,

```
:secret => '<some_long_alpha_numeric_string>'

```

}

Also, in Rails 2.x, the default session store is cookies:

[http://ryandaigle.com/articles/2007/2/21/what-s-new-in-edge-rails-cookie-based-sessions](http://ryandaigle.com/articles/2007/2/21/what-s-new-in-edge-rails-cookie-based-sessions)

Regards, Craig

---

<div class="post-metadata">

**Author:** ![11175](https://avatars.discourse-cdn.com/v4/letter/1/8edcca/32.png) [@11175](https://discuss.rubyonrails.org/u/11175)\
**Post date:** [October 8, 2008, 2:58pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/8 "2008-10-08T14:58:10Z")

</div>

Craig Demyanovich wrote:

> Out of curiosity, do you have a config.action\_controller.session entry in config/environment.rb? It should look something like:
> 
> &nbsp;&nbsp;config.action\_controller.session = { &nbsp;&nbsp;&nbsp;&nbsp;:session\_key =\> '\_\<your\_app\_name\>\_session', &nbsp;&nbsp;&nbsp;&nbsp;:secret =\> '\<some\_long\_alpha\_numeric\_string\>' &nbsp;&nbsp;}
> 
> Also, in Rails 2.x, the default session store is cookies:
> 
> [http://ryandaigle.com/articles/2007/2/21/what-s-new-in-edge-rails-cookie-based-sessions](http://ryandaigle.com/articles/2007/2/21/what-s-new-in-edge-rails-cookie-based-sessions)
> 
> Regards, Craig

I do have that in my envirnments.rn, however, my session\_key says:

=\>\_newen\_session

and that isn't the name of my app. My app name is new\_trunk[trunk], should it be named something else?

---

<div class="post-metadata">

**Author:** ![Craig\_Demyanovich](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@Craig\_Demyanovich](https://discuss.rubyonrails.org/u/Craig_Demyanovich)\
**Post date:** [October 8, 2008, 5:15pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/9 "2008-10-08T17:15:49Z")

</div>

I don’t know if the session\_key needs to match your app name. You could change it to match and see what happens.

Craig

---

<div class="post-metadata">

**Author:** ![11175](https://avatars.discourse-cdn.com/v4/letter/1/8edcca/32.png) [@11175](https://discuss.rubyonrails.org/u/11175)\
**Post date:** [October 8, 2008, 6:13pm UTC](https://discuss.rubyonrails.org/t/recent-upgrade-to-2-1-0-not-working-ie7/35130/10 "2008-10-08T18:13:19Z")

</div>

Nevermind, I don't think it's still saving any sessions. If I changed the session name to session[:dude] I got the same ol' nil refernce which says to me that it wasn't saved, although it does seem to recgonize session[:user] which is a little strange. . .
