Login engine not working

I had another Linux installation on which I had both the Login and User
engines working perfectly. Then, I copied the entire Rails folder
(including /vendor/plugins off root which included all my plugins) to a
different installation.

The new installation was slightly different, so I had a few problems
with it being Rails v. 1.1.4 (I just changed to RAILS_GEM_VERSION =
‘1.1.4’ from 1.1.2) and the MySQL sock being in a different place (just
added socket: /var/lib/mysql/mysql.sock to database.yml).

So everything opens up nicely, and my application is running. Then, when
I go to log in to the protected section, the Login Engine appears to not
work and I get the login page refreshed, whatever I put in. No notice
appears informing me of a bad input either. Also, I tried to load
several protected pages after that, but Login Engine had obviously not
done what I wanted.

How do I go about fixing/testing what’s wrong? I’d rather not reinstall
all the engines…

Isaac Rowntree wrote:

I had another Linux installation on which I had both the Login and User
engines working perfectly. Then, I copied the entire Rails folder
(including /vendor/plugins off root which included all my plugins) to a
different installation.

The new installation was slightly different, so I had a few problems
with it being Rails v. 1.1.4 (I just changed to RAILS_GEM_VERSION =
‘1.1.4’ from 1.1.2) and the MySQL sock being in a different place (just
added socket: /var/lib/mysql/mysql.sock to database.yml).

So everything opens up nicely, and my application is running. Then, when
I go to log in to the protected section, the Login Engine appears to not
work and I get the login page refreshed, whatever I put in. No notice
appears informing me of a bad input either. Also, I tried to load
several protected pages after that, but Login Engine had obviously not
done what I wanted.

How do I go about fixing/testing what’s wrong? I’d rather not reinstall
all the engines…

I forgot to add - I also copied the entire database across and that
reverting to the previous installation is no longer an option :frowning:

You’ll need to look at the access logs from some clue about what might
be going wrong - see if there’s anything suspicious in there.

  • james

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs