On Fri, Sep 23, 2011 at 7:04 AM, Martin Wawrusch 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 produ
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
On Thu, Sep 22, 2011 at 8:57 PM, Everaldo Gomes
wrote:
> Hi!
> Take a look in the omni populus gem:
> https://github.com/icelab/omnipopulus
Hey!
I've just tried it and had the same result.
I wonder if twitter might have changed something on their side for
authenticating apps or if is omniauth on i
Hi!
Take a look in the omni populus gem:
https://github.com/icelab/omnipopulus
Best Regards,
Everaldo
On Thu, Sep 22, 2011 at 8:54 PM, Leonardo Mateo wrote:
> Hi guys,
> I've been struggling with OmniAuth for Twitter for a past few days and
> I can't get it to work with Rails 3.1
> I'm not su
Hi guys,
I've been struggling with OmniAuth for Twitter for a past few days and
I can't get it to work with Rails 3.1
I'm not sure if this is a Twitter problem, or an OmniAuth problem.
I create the application on twitter, the steps vary a bit from the
Railscast showing it, but that's because of a
5 matches
Mail list logo