Rails doesn't create sessions in production

Rails
1

I’m having an issue with sessions in the 1.2 pre-release code.
Sessions are created when the site is in development mode, and they
are not created when the site is in production mode. I’m using a
database store, but even when I switch back to the file system store,
sessions are not created. The only difference in the way that I am
running rails is that I switch to production mode with
“RAILS_ENV=production script/server”

Where should I begin looking first?

2

On Nov 13, 2006, at 12:00 PM, Bryan L. wrote:

I’m having an issue with sessions in the 1.2 pre-release code.
Sessions are created when the site is in development mode, and they
are not created when the site is in production mode. I’m using a
database store, but even when I switch back to the file system store,
sessions are not created. The only difference in the way that I am
running rails is that I switch to production mode with
“RAILS_ENV=production script/server”

Where should I begin looking first?

I’m going to answer my own question.

I had a plugin installed that changed the location of the sql session
store. (sneaky plugin developers!)

3

Bryan L. wrote:

On Nov 13, 2006, at 12:00 PM, Bryan L. wrote:

I had a plugin installed that changed the location of the sql session
store. (sneaky plugin developers!)

Accountability please - which plugin?

4

On Nov 13, 2006, at 2:04 PM, Daniel Collis-puro wrote:

Bryan L. wrote:

On Nov 13, 2006, at 12:00 PM, Bryan L. wrote:

I had a plugin installed that changed the location of the sql session
store. (sneaky plugin developers!)

Accountability please - which plugin?

I’m not going to say here, but I have followed up with the developer,
and hopefully he will make the changes in his documentation.

5

Bryan L. wrote:

I’m not going to say here, but I have followed up with the developer,
and hopefully he will make the changes in his documentation.

I don’t understand this. You know of a bug that’s probably a pretty
difficult one to catch, yet you won’t disclose it? We’re in the open
source/free software world here - disclosure is our middle name.

If you’re worried about embarassing the author, don’t be. If the author
is so thin-skinned that they won’t take critcism in stride, they
shouldn’t make code freely available.

6

If you’re worried about embarassing the author, don’t be. If the author
is so thin-skinned that they won’t take critcism in stride, they
shouldn’t make code freely available.

I could not agree more. We are pulling our hair trying to fix this very
problem, would you please make the solution available?