Setting up sunspot geolocation scenario - sunspot

I am using Sunspot for searching and using Geocoder for addresses and then for calculating distances, Geokit-rails3.
class Product < ActiveRecord::Base
belongs_to :store
searchable do
text :name
end
end
class Store < ActiveRecord::Base
acts_as_mappable
geocoded_by :address, :latitude => :lat, :longitude => :lng
attr_accessible :lat, :lng, :address
has_many :products
end
Question
What I want when typing in a product to search for is also the ability to type an address inside of another field to search for products in that given area with a 30 mile radius.
This is my controller which allows me to search for Products:
class SearchController < ApplicationController
def index
#search = Product.search do |q|
q.fulltext params[:search]
end
#products = #search.results
end
end
So I believe the form would look something like this after I am done:
<%= form_tag search_path, :method => 'get' do %>
<%= text_field_tag :search, params[:search]" %>
<%= submit_tag "Search", :name => nil %>
<p> Search Near: </p>
<%= label_tag :location, "Search nearby an Address" %>
<%= text_field_tag :location, params[:location] %>
<% end %>
I am thinking :location would serve as a virtual attribute for the Stores :address in order for the field to be mapped correctly but this is all speculation.
How do I set this all up in order to achieve the specific scenario?

Related

how search with simple_form_for and pg_search gem

Rails : 5.1.4
I'm trying to search on :immo_type or/and :address
class SearchesController < ApplicationController
def home
#search = Purchase.find(params[:immo_type])
#purchases = Purchase.where("immo_type ILIKE ?", "%#{#search}%")
end
def index
#purchases = Purchase.all
#spurchases = Purchase.search_by_immo_type_and_address('#search')
end
end
From the view i used simple_form_for. I don't know how to see how to access the content of params[:immo_type]. When i used rails, i've this message
Couldn't find Purchase with 'id'=
I can see all my purchases with Purchase.all
<%= simple_form_for :immo_type, url: searches_url, method: :get do |f| %>
<%= f.hidden_field :immo_type, params[:immo_type] %>
<%= f.input :address, placeholder: 'Town', label: "Where" %>
<%= f.input :immo_type, placeholder: 'flat, house', label: "Flat or house" %>
<%= f.button :submit, "Rechercher", class: "btn btn-danger" %>
<% end %>
Here my models
class Purchase < ApplicationRecord
include PgSearch
pg_search_scope :search_by_immo_type_and_address, against: [:immo_type, :address]
belongs_to :user
has_many :users, :through => :searches
end
class Search < ApplicationRecord
belongs_to :user
belongs_to :leasing
belongs_to :purchase
end
I would like to search from my home.html.erb (root pages) and display the result on my index.html.erb
SearchesIndex
<ul>
<% #purchases.each do |purchase| %>
<li><%= link_to purchase.address %></li>
maison ou appartement : <%= purchase.immo_type %><br>
prix : entre <%= purchase.price_min %> et <%= purchase.price_max %><br>
<% end %>
</ul>
So, first i need to work with a search controller with the home and index views
class SearchesController < ApplicationController
def home
#searches = params[:immo_type]
end
def index
#purchases = Purchase.search_by_immo_type_and_address("#{params[:purchase][:immo_type]}")
end
end
This is my purchase model with Pg_Search gem
class Purchase < ApplicationRecord
belongs_to :user
has_many :users, :through => :searches
include PgSearch
pg_search_scope :search_by_immo_type_and_address, against: [:immo_type]
end
And the view with simple_form_for
<%= simple_form_for :purchase, url: searches_url, method: :get do |f| %>
<%= f.input :address %>
<%= f.input :immo_type %>
<%= f.button :submit, "Rechercher"%>
<% end %>
I hope it can help you !

In RoR, f.fields_for is rendering as nothing

I’m using Rails 4.2.7. In my model I have
class MyObject < ActiveRecord::Base
…
belongs_to :address, :autosave => true, dependent: :destroy
accepts_nested_attributes_for :address, :my_object_times
and the address model
class Address < ActiveRecord::Base
belongs_to :state
belongs_to :country
...
has_one :my_object
end
I want to write a form that will allow me to build both the child and parent objects, so I tried
<%= form_for #my_object, :url => my_objects_create_path, :remote => true do |f| %>
<div class="field">
<%= f.fields_for :address do |addr| %>
<%= addr.label :address %> <span name="my_object[address]_errors"></span><br>
City: <%= addr.text_field :city %>
<%= addr.select :state, options_for_select(us_states.collect{|s| [ s.name, s.id ]}), {:prompt => "Select State"} %>
<%= country_code_select('my_object[address]', 'country_id',
[[ 'US', 'United States' ], [ 'CA', 'Canada' ]],
{:include_blank=>true, :selected => #default_country_selected.id},
{:class=>'countryField'}
) %>
<% end %>
</div>
but the above is rendered as only
<div class="field">
</div>
How do I adjust things so that my fields render AND I'm able to create my object in my controller using
my_object = MyObject.new(params)
Edit: Per the answer given, I tried
#my_object.address.build
from teh controller action taht rendres the form, but got the erorr
undefined method `build' for nil:NilClass
#this is in form loading class
def new
#myobject = MyObject.new
#myobject.address = Address.new
end
#Now you can use nested attribute for Address
<%=form_for(#myobject) do |f|%>
<%=f.fields_for :address do |a|%>
Your form fields here
<%end%>
<%end%>
#this is create def
def create
#myobject = MyObject.new(myobject_params)
#myobject.save
end
#in params
def myobject_params
params.require(:myobject).permit(:some, :key,:of, :myobject, :address_attributes[:address, :attribute])
end
#this should work
If my_object has no addresses, then nothing will be rendered. This is default behavior in Rails. One way to get around this is to build one or more empty children in the controller so that at least one set of fields is shown to the user
The Rails guides talk about this in Nested Forms section 9.2
Also, in your MyObject model, i think it should be has_one address. you have belongs_to
class MyObject < ActiveRecord::Base
has_one :address, :autosave => true, dependent: :destroy
accepts_nested_attributes_for :address
end

4.2 Without cocoon, simple form or formtastic? Nested forms cookbook

I struggle with nested forms.
There're three classes Recipe, Quantity and Ingredient:
class Recipe < ActiveRecord::Base
belongs_to :user
has_many :quantities
has_many :ingredients, through: :quantities
accepts_nested_attributes_for :quantities
class Quantity < ActiveRecord::Base
belongs_to :recipe
belongs_to :ingredient
accepts_nested_attributes_for :ingredient, :reject_if => :all_blank
class Ingredient < ActiveRecord::Base
has_many :quantities
has_many :recipes, :through => :quantities
Recipe Controller
def new
#recipe = current_user.recipes.build
#quantity = #recipe.quantities.build
end
def create
#recipe = current_user.recipes.build(recipe_params)
if #recipe.save
redirect_to #recipe
else
render 'new'
end
end
private
def recipe_params
params.require(:recipe).permit(
:name,
quantities_attributes: [:id, :amount, :ingredient_id],
)
end
View for recipe#new
<%= form_for #recipe, html: {class: "form-horizontal"} do |f| %>
<li class="control-group">
<%= f.label :name, "Recipe Name", class: "control-label" %>
<div class="controls"><%= f.text_field :name %></div>
</li>
<%= f.fields_for :quantities do |quantity| %>
<%= render 'quantity_fields', f: quantity %>
<% end %>
<%= f.submit %>
<% end %>
_quantity_fields
<%= f.label :amount, "Amount:" %>
<%= f.text_field :amount %>
Here should follow a Select input with content from Ingredient and the POST request should insert the ingredient_id in the column of Quantity.
<%= f.select("ingredient_id", "ingredient_id", Ingredient.all.collect
{|p| [ p.name, p.id ] }, {include_blank: 'Choose'}) %>
getting
NoMethodError in Recipes#new
Showing C:/Sites/4.2/sample_app - Kopie/app/views/recipes/_quantity_fields.html.erb
where line #6 raised:
undefined method `merge' for [["Sugar", 1], ["Butter", 2]]:Array
Any ideas? Thanks!
<%= f.collection_select(:ingredient_id, Ingredient.all, :id, :name) %>
solved the select statement
but how can I create multiple quantities here?

Devise Registration not showing "some" nested form fields Rails 4

I've got a modified Devise "sign_up" form (new registration) that includes fields for child and grandchild objects to be created along with the user. All of the model relationships are set up properly with access to the child's attributes. However, when the form renders, only the fields for the Devise user and one of the grandchildren is shown.
When a User is created, he/she will automatically be assigned a Customer object, an Account object, and an Address object. As you can see by the relationships in the User model below, User has one Customer and Customer has many Accounts and one Address. There was previously an issue with rendering the form at all, which I solved by changing the values passed to the builder method. WHY WON'T THIS WORK??? This is what I have so far:
*user.rb
class User < ActiveRecord::Base
before_create :generate_id
# Virtual attribute for authenticating by either username or email
# This is in addition to a real persisted field like 'username'
attr_accessor :login
has_one :customer, :dependent => :destroy
has_many :accounts, through: :customer
accepts_nested_attributes_for :customer, :allow_destroy => true
accepts_nested_attributes_for :accounts, :allow_destroy => true
has_one :address, through: :customer
accepts_nested_attributes_for :customer, :allow_destroy => true
accepts_nested_attributes_for :address, :allow_destroy => true
has_one :administrator
validates_uniqueness_of :email, :case_sensitive => false
validates_uniqueness_of :id
validates :username,
:presence => true,
:uniqueness=> {
:case_sensitive => false
}
# User ID is a generated uuid
include ActiveUUID::UUID
natural_key :user_id, :remember_created_at
belongs_to :user
# specify custom UUID namespace for the natural key
uuid_namespace "1dd74dd0-d116-11e0-99c7-5ac5d975667e"
# Include default devise modules. Others available are:
# :confirmable, :lockable, :timeoutable and :omniauthable
devise :database_authenticatable, :registerable, :timeoutable, :recoverable, :trackable, :validatable
# Generate a random uuid for new user id creation
def generate_id
self.id = SecureRandom.uuid
end
# Allow signin by either email or username ("lower" function might have to be removed?)
def self.find_for_database_authentication(warden_conditions)
conditions = warden_conditions.dup
if login = conditions.delete(:login)
where(conditions.to_h).where(["lower(username) = :value OR lower(email) = :value", { :value => login.downcase }]).first
else
where(conditions.to_h).first
end
end
end
registrations_controller.rb
class RegistrationsController < Devise::RegistrationsController
before_filter :configure_permitted_parameters
# GET /users/sign_up
def new
#user = User.new
build_resource({})
self.resource[:customer => Customer.new, :account => Account.new, :address => Address.new]
respond_with self.resource
end
def create
#user = User.new
# Override Devise default behavior and create a customer, account, and address as well
resource = build_resource(params[:sign_up])
if(resource.save)
sign_in(resource_name, resource)
respond_with resource, :location => after_sign_up_path_for(resource)
else
render :action => "new"
end
end
protected
def configure_permitted_parameters
devise_parameter_sanitizer.for(:sign_up) { |u|
u.permit(:username, :email, :password, :password_confirmation,
customer_attributes: [:title, :firstname, :lastname, :phone1, :phone2],
account_attributes: [:acct_type],
address_attributes: [:address1, :address2, :zip_code])
}
end
end
application_controller.rb
class ApplicationController < ActionController::Base
# Prevent CSRF attacks by raising an exception.
# For APIs, you may want to use :null_session instead.
protect_from_forgery with: :exception
before_filter :configure_permitted_parameters, if: :devise_controller?
def after_sign_in_path_for(resource)
if current_user.role == 'admin'
adminview_administrator_path(current_user, format: :html)
else
accounts_path(current_user, format: :html)
end
end
protected
def configure_permitted_parameters
devise_parameter_sanitizer.for(:sign_up) { |u| u.permit(:username, :email, :password, :password_confirmation,
customer_attributes: [:title, :firstname, :lastname, :phone1, :phone2],
account_attributes: [:acct_type],
address_attributes: [:address1, :address2, :zip_code]) }
devise_parameter_sanitizer.for(:sign_in) { |u| u.permit(:login, :username, :email, :password) }
devise_parameter_sanitizer.for(:account_update) { |u| u.permit(:username, :email, :password, :password_confirmation, :current_password) }
end
end
views/devise/registrations/new.html.erb
<h1>Create an account</h1>
<div class="panel panel-default" style="width: 50%; padding: 0 25px;">
<%= bootstrap_nested_form_for(resource, as: resource_name, url: user_registration_path(resource_name)) do |f| %>
<%= devise_error_messages! %>
<h3>User Info</h3>
<!-- fields for User object -->
<%= f.text_field :username, autofocus: true %>
<%= f.email_field :email %>
<%= f.password_field :password , autocomplete: "off"%>
<% if #validatable %>
<em>(<%= #minimum_password_length %> characters minimum)</em>
<% end %><br />
<%= f.password_field :password_confirmation, autocomplete: "off" %>
<!-- fields for Customer object -->
<%= f.fields_for :customer do |customer_fields| %>
<%= customer_fields.text_field :title %>
<%= customer_fields.text_field :firstname %>
<%= customer_fields.text_field :lastname %>
<%= customer_fields.text_field :phone1 %>
<%= customer_fields.text_field :phone2 %>
<% end %>
<!-- fields for Account object -->
<%= f.fields_for :account do |account_fields| %>
<%= account_fields.text_field :acct_type %>
<% end %>
<!-- fields for Address object -->
<%= f.fields_for :address do |address_fields| %>
<%= address_fields.text_field :address1 %>
<%= address_fields.text_field :address2 %>
<%= address_fields.text_field :zip_code %>
<% end %>
<br />
<div class="actions">
<%= f.submit "Create My Account", :class => "btn btn-info" %>
</div>
<% end %>
</div>
</div>
Again, the above view does render, but the form only displays the fields for Devise new user and the one field (acct_type) for the account fields. How to get the rest of form to display and create all of these things on submission? Everything I've tried and everything I've read leads me to think that there's a problem with Rails 4's strong_parameters not being able to recognize the permitted attributes (see above controllers) in an array. Could that be the issue? If so, how does one go about passing the parameters necessary to build all these things?
Could be problem with the routes?
routes.rb
Rails.application.routes.draw do
devise_for :users, :controllers => { :registrations => "registrations" }
devise_scope :user do
# authentication
post "/accounts/adminview" => "devise/sessions#new"
end
root 'home#index'
resources :administrators do
member do
get :adminview
end
end
resources :users do
resource :customers
resource :accounts
resource :addresses
end
resources :account_types, :accounts, :addresses, :administrators, :customers, :transaction_types, :transactions, :users
end
I've tried every combination of ways that I could find on SO. This has taken up days worth of valuable time. I don't see any reason why it can't work. Does anyone have a better way of doing this? Is there a gem that would help? I'm willing to tear Devise apart and rebuild if necessary.
F.Y.I. It's Rails 4 and Devise 3.4.1. I've also added nested_form gem, but it doesn't make a difference.
Thank you
If you raise your params in controller you probably see accounts_attributes instead account_attributes you are setting in permit at application_controller, try replace it.

Simple Search with Rails - Search Results on Separate Page

Im starting out in rails and trying to incorporate a simple search but am only getting so far.
the string looks ok but doesn't seem to execute to the results page. there seems to be a number of issues nil methods, actions missing or routes falling over when I try include restful resources.
I want search on one page (search) and the results to populate to another results page (map).
Both come under the PagesController and are actions within it.
The table is called towns and the user entries and CRUD area it is controlled by the TownsController and has an association with devise User_id.
There is then the pages controller which has search,map,about,contact pages.
class PagesController < ApplicationController
def index
end
def search
#towns = Town.search(params[:search])
end
def page
end
def map
end
end
--------------------------
class Town < ActiveRecord::Base
geocoded_by :name
after_validation :geocode
belongs_to :user
def self.search(search)
if search
search_condition = "%" + search + "%"
where(['townName LIKE ? OR townDescription LIKE ?', search_condition, search_condition])
end
end
-------------------------
views
search.html.erb
<div class="form-group">
<%= form_tag(pages_map_path , method: "get") do %>
<p>
<%= text_field_tag :search, params[:search], class: 'search-text' %>
<%= submit_tag "Search", :name => nil, class: 'btn btn-primary btn-lg'%>
</p>
<% end %>
results --> to map page
map.html.erb
<ul>
<% #towns.each do |town| %>
<li><%= link_to town.name,
:action => 'map', :id => town.id %></li>
<% end %>
</ul>
---------------------------
routes
Rails.application.routes.draw do
devise_for :users
get "pages/search"
get "pages/index"
get "pages/contact"
get "pages/about"
get "pages/map"
get "pages/page"
match ':controller(/:action(/:id))', :via => [:get, :post]
root 'pages#search'
end
Solution:
Column names in search query were incorrect
townName LIKE ? OR townDescription should be = name LIKE ? OR description
updated results page call to:
<ul>
<% #towns.each do |town| %>
<h2><li><%= link_to #name, controller: 'towns', :action => 'show', :id => town.id %></li></h2>
<% end %>
</ul>