Hi

is it possible to have two separate uses of location on a site? let me explain that a bit: I want to have one content_type which users geolocate by using the map and clicking on the required location. on a second content_type I want users to add the street address and have the geolocation generated. So far i can do on or other of these, but not both in parallel on two content_types. Is this at all possible??

Additionally, and this probably a really noob question, i would like in both cases to not have the latitude and longitude inputs - how can these be hidden?

thanks

Comments

yesct’s picture

yesct commented
Title: two different uses of location on one site » per content type two different uses of location on one site

I'm using cck locations. So for content type 1, I can pick to allow the coordinate chooser under locative information, collection settings in the cck content type field edit page. And I can pick different options for content type 2, that I add a different location cck field to.

To disallow lat long inputs, change the settings under collection settings to "do not collect". But I dont know how this influences storing the geocoding result.

yesct’s picture

yesct commented
Issue tags: +location collection settings require allow etc
rooby’s picture

rooby commented
Status: Active » Fixed

Geocoding will still occur iven if you have chosen not to collect the coordinates, so for the geocode content type on your location collection settings select "Do not collect" for the "Coordinate Chooser", this will mean the user doesn't can't select the coordinates. But the geocoding will still happen on save and you will get the coordinates that way.

Then for the other content type select "Allow" or "Required" or something for the "Coordinate Chooser" so the user can enter the coordinates. Now if the user enters coordinates no geocoding will be done. However if the user doesn't enter coordinates geocoding will be done.
So if you never want geocoding then make the coordinate chooser "Required".

IN terms of hiding the fields, the first content type will already have no fields.
The second content type needs the fields, because the map javascript needs to enter its coordinates into the fields. This means you will just have to hide them using css. Just add
display: none;
for the fields you want hidden.

All this will work with node or cck locations.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

dreamleader’s picture

dreamleader commented

Sorry, for posting here. I've removed original text.

rooby’s picture

rooby commented

@dreamleader:
In addition to opening new issues instead of tacking onto old unrelated ones, it is also best to only post a question once, in one issue.

(I have answered your question in the other issue.)

rooby’s picture

rooby commented

That's ok, you have to start somewhere.
No need to remove it.