Note that there are some explanatory texts on larger screens.

plurals
  1. PORails, OpenID and Authlogic
    text
    copied!<p>I've been following <a href="http://railscasts.com/episodes/170-openid-with-authlogic" rel="nofollow noreferrer">ryan baytes screencast #170</a> and adding <a href="http://github.com/pelle/ruby-openid" rel="nofollow noreferrer">ruby-openid</a>, <a href="http://github.com/binarylogic/authlogic" rel="nofollow noreferrer">authlogic</a> and <a href="http://github.com/binarylogic/authlogic_openid" rel="nofollow noreferrer">authlogic-oid</a> to an existing authlogic authentication system.</p> <p>However, i keep getting the following stack of errors:</p> <p>NameError (uninitialized constant OpenIdAuthentication::InvalidOpenId): /Library/Ruby/Gems/1.8/gems/authlogic-oid-1.0.4/lib/authlogic_openid/session.rb:53:in <code>openid_identifier=' /Library/Ruby/Gems/1.8/gems/authlogic-oid-1.0.4/lib/authlogic_openid/session.rb:47:in</code>credentials=' authlogic (2.1.2) lib/authlogic/session/foundation.rb:28:in <code>initialize' authlogic (2.1.2) lib/authlogic/session/password.rb:140:in</code>initialize' authlogic (2.1.2) lib/authlogic/session/activation.rb:48:in <code>initialize' authlogic (2.1.2) lib/authlogic/session/klass.rb:61:in</code>initialize' authlogic (2.1.2) lib/authlogic/session/scopes.rb:79:in <code>initialize' app/controllers/user_sessions_controller.rb:10:in</code>new' app/controllers/user_sessions_controller.rb:10:in `create'</p> <p>Is there anyone who's facing the same kind of problem? i'm using rails 2.3.4</p> <p>I've tried <a href="http://github.com/binarylogic/authlogic_openid" rel="nofollow noreferrer">binary's example app</a> which is working perfectly well (rails 2.1.2), i've tried <a href="http://asciicasts.com/episodes/170-openid-with-authlogic" rel="nofollow noreferrer">the code provided by ryan bates</a> and it is working well too (rails 2.3.2). So, the libraries are working with previous versions of rails.</p> <p>Any clues?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload