Getting this error when I try to sign up on a new Tracks installation, trunk/SVN today, on 10.4.8.

Any ideas?

Check your config/environment.rb file. Do you have a line:


AUTHENTICATION_SCHEMES = [‘database’]


If you’re trying to use the usual database method of authentication (i.e. not OpenID or ldap), that’s what you need there.

Yes, I have that line and it is not commented out.

I’m not sure what the problem is then. What database are you trying to use? It’s not an error that I’ve come across before.

The error happens when the user is being validated and checks that the auth_type field matches one of the schemes specified in your environment.rb. In the signup process, it looks like we don’t explicitly set the auth_type, which suggests that the default value in the schema is supplying it.

Looking at this code, it certainly seems likely there are bugs to be found here. However, I can’t replicate the issue you’re describing. I think bsags question is a good one: what database are you using?

lukemelia - 10 March 2007 10:10 PM

The error happens when the user is being validated and checks that the auth_type field matches one of the schemes specified in your environment.rb. In the signup process, it looks like we don’t explicitly set the auth_type, which suggests that the default value in the schema is supplying it.

Looking at this code, it certainly seems likely there are bugs to be found here. However, I can’t replicate the issue you’re describing. I think bsags question is a good one: what database are you using?

sqlite3.

Turns out this works on Linux (Ubuntu) but doesn’t work on Mac OS X.  There must be something i’m missing but I can’t find it.  The configurations are identical.

Strange. I cannot replicate this with sqlite3 on my mac.

I’ve ashed my Tracks install and grabbed a fresh copy from SVN.  The problem still occurs.  I don’t think I have any inconsistencies on my install on RoR.  How can I help you get more information to solve the problem?

Let me try harder to replicate it:

Please post:

* the version of sqlite3 you have (type “sqlite3 -version”)
* the version of the sqlite3-ruby gem (type “gem list sqlite3-ruby”)
* a list of the exact steps you take after exporting from SVN

Cheers,
Luke

vertice:~ tim$ sqlite3 -version
3.3.13
vertice:~ tim$ gem list sqlite3-ruby

*** LOCAL GEMS ***

sqlite3-ruby (1.2.1, 1.2.0, 1.1.0)
  SQLite3/Ruby is a module to allow Ruby scripts to interface with a
  SQLite3 database.
vertice:~ tim$

svn co—username=guest http://dev.rousette.org.uk/svn/tracks-repos/trunk .

[output snipped]

cd tracks
mv log.tmpl log
cd config
mate environment.rb.tmpl
[save with a changed SALT]
mate database.rb.tmpl
[save with a correct db statement:

development:
  adapter: sqlite3
  database: tracks

test:
  adapter: sqlite3
  database: “:memory:“

production:
  adapter: sqlite3
  database: tracks
]

mv the tmpl files to the correct files
cd ..
script/server -e production

Did you do a rake db:migrate somewhere in there?

yup, sorry, right before script/server -e production, rake db:migrate occurs.

Unfortunately, I’ll be on the road the rest of the week away from my mac. I’ll pick this up when I return next week.

Any news?

well?