Rails 3.2.rc1 ActiveRecord ConnectionNotEstablished about acts_as_geocodable HOT 4 CLOSED

I'm guessing something has changed with when ActiveRecord connects initially.

We'll look at it when we can, but patches are always welcome if you can't wait!

-Daniel

Daniel Morrison
[i] Collective Idea
http://collectiveidea.com
http://ideafoundry.info
25 West 8th Street, Suite 200
Holland, MI 49423
616-990-0155
[email protected]

On Dec 20, 2011, at 8:34 AM, kaluznyo wrote:

When I try to launch my server (rails s) I got this error with rails 3.2.rc1 :

https://gist.github.com/a99d0ac6ce164d547618

I note very sure if it's related to acts_as_geocodable or rails. But if I launche my app without your gem, this error disapear.

Juste in case, my issue on Rails repo : rails/rails#4046

---

Reply to this email directly or view it on GitHub:
#18

from acts_as_geocodable.

Okay thanks, A simple workaround exist

# Gemfile
gem 'acts_as_geocodable', :require => false

# config/initialisers/acts_as_geocodable.rb
require 'acts_as_geocodable'

UPDATE
And the gem acts-as-taggable-on have the same issue, some idea to fix :
mbleigh/acts-as-taggable-on#211

from acts_as_geocodable.

Okay, now it's not a bug anymore. The rails team have fixed it, in rails-3-2 branch. So it's must be Ok for the next rails 3.2 version (rc2 or final)

Thanks

from acts_as_geocodable.

Hi there! We’re doing some open source maintenance work and closing old issues. If you would still like this issue to be addressed, please re-create it by May 17, 2017. Thanks!

from acts_as_geocodable.