On Fri, Sep 23, 2011 at 7:04 AM, Martin Wawrusch <mar...@wawrusch.com> wrote: > I remember having had some trouble as well. > Make sure that you use the following in your gem files: > devise: ~=1.4.2 > ominauth: =0.2.5 (not 0.2.6 for some reason because that has a dependency > conflict with another lib) > In your production.rb do something like this at the top: > require 'pg' > require 'net/http' > require 'openssl' > OpenSSL::SSL:VERIFY_PEER = OpenSSL::SLL:VERIFY_NONE > This is a bit of a hack but was the only way for me to get this to work in > my configuration (after spending half a day investigating) Hi Martin, That didn't work for me. Anywho, it seems to be a twitter issue, because I'm being able to authenticate with GitHub. It looks like a nice debugging case for OmniAuth, but I'm not sure if it worth it, since has been announced big architectural changes for version 1.0. Maybe this is fixed there, but I don't know how long version 1.0 will take. Does anyone knows about it?
Thanks a lot in advance. -- Leonardo Mateo. There's no place like ~ -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
