uninitialized constant ParseGeoPoint #56

Closed
ivanhoe opened this Issue Jan 13, 2013 · 7 comments

Comments

Projects
None yet
4 participants

ivanhoe commented Jan 13, 2013

Hi guys,

Im trying to use use the class ParseGeoPoint in a controller like the next one:

  1. require 'parse_resource'
  2. class HomeController < ApplicationController
    
  3. def index
    
  4.   ParseResource::Base.load!("app_id", "master_key")
    
  5.   place = Place.new
    
  6.   place.name = "Office"
    
  7.   place.location = ParseGeoPoint.new  
    
  8. end
12.end

But im getting the next error:

NameError (uninitialized constant HomeController::ParseGeoPoint):
app/controllers/home_controller.rb:9:in `index'

Is there any problem with this code?

Owner

adelevie commented Jan 13, 2013

Are you sure you are using the correct version?

Sent from my iPhone

On Jan 13, 2013, at 1:28 PM, Ivan Alvarez Frias notifications@github.com wrote:

Hi guys,

Im trying to use use the class ParseGeoPoint in a controller like the next one:

require 'parse_resource'
class HomeController < ApplicationController
def index
ParseResource::Base.load!("app_id", "master_key")
place = Place.new
place.name = "Office"
place.location = ParseGeoPoint.new
end 11. 12.end
But im getting the next error:

NameError (uninitialized constant HomeController::ParseGeoPoint):
app/controllers/home_controller.rb:9:in `index'

Is there any problem with this code?


Reply to this email directly or view it on GitHub.

ivanhoe commented Jan 13, 2013

My environment is:

ruby 1.9.2p320 (2012-04-20 revision 35421) [x86_64-darwin11.3.0]
Rails 3.2.9

My gem file:

source 'https://rubygems.org'

gem 'rails', '3.2.9'

gem 'foreigner'
gem 'pg'
gem 'thin'
gem 'activeadmin', '0.5.0'
gem 'devise'
gem "parse_resource", "~> 1.7.2"
gem 'nestful'
gem 'roo'

group :assets do
gem 'sass-rails', '> 3.2.3'
gem 'coffee-rails', '
> 3.2.1'
gem 'uglifier', '>= 1.0.3'
end

gem 'jquery-rails'

Collaborator

jamonholmgren commented Feb 23, 2013

@ivanhoe Is this still an issue?

copperx commented Apr 8, 2013

It is for me! I can't figure out what's the problem.

Any pointers?

Collaborator

jamonholmgren commented Apr 17, 2013

No idea...!

copperx commented Apr 17, 2013

I looked at the source downloaded from the gem, it IS the right version, but the code ISN'T.

Maybe up the version number and recreate the gem?

Collaborator

jamonholmgren commented Apr 17, 2013

We're very close to a merge of a big pull request. We'll push up a new gem once we do and hopefully that fixes it. I don't have access to push up RubyGem builds, so that will be an @adelevie thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment