Hi everyone, I have a content type that should have a Location field. But, instead of the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations. I've managed to create a string field that allows the user to choose from his list and contains the location ID. The problem is that in this method Drupal doesn't recognize it as a Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
1. When the user create the node, he will choose from his list, but Drupal will save it as it would save a node with new location. 2. The data would be saved in the same method I'm using now (string field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
If I understand your problem correctly, I think I'd make two content types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead of the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations. I've managed to create a string field that allows the user to choose from his list and contains the location ID. The problem is that in this method Drupal doesn't recognize it as a Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it: 1. When the user create the node, he will choose from his list, but Drupal will save it as it would save a node with new location. 2. The data would be saved in the same method I'm using now (string field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
Hi Joel, First- thank you!
So if I undestand you correctly, I have one type that contain just the location and the title, and another which is my main type that contains all the information needed as well as a reference to the first type. But - I want every user to have its own locations list. So should I allow them to make a list of nodes of first content type?
On Wed, Aug 15, 2012 at 3:42 PM, Joel Willers joel.willers@sigler.com wrote:
If I understand your problem correctly, I think I'd make two content types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead of the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations. I've managed to create a string field that allows the user to choose from his list and contains the location ID. The problem is that in this method Drupal doesn't recognize it as a Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
- When the user create the node, he will choose from his list, but Drupal will save it as it would save a node with new location.
- The data would be saved in the same method I'm using now (string field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
-- [ Drupal support list | http://lists.drupal.org/ ]
Seems like a good solution to me. You can even make a View that will show in the list of potential locations only the locations that the user has made (a bit advanced, but all done through the UI).
Good luck!
Joel
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 7:55 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi Joel, First- thank you!
So if I undestand you correctly, I have one type that contain just the location and the title, and another which is my main type that contains all the information needed as well as a reference to the first type. But - I want every user to have its own locations list. So should I allow them to make a list of nodes of first content type?
On Wed, Aug 15, 2012 at 3:42 PM, Joel Willers joel.willers@sigler.com wrote:
If I understand your problem correctly, I think I'd make two content types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead of the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations. I've managed to create a string field that allows the user to choose from his list and contains the location ID. The problem is that in this method Drupal doesn't recognize it as a Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
- When the user create the node, he will choose from his list, but Drupal will save it as it would save a node with new location.
- The data would be saved in the same method I'm using now (string field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
Hi again, So- I've tried your suggestion, and it seems to work almost perfectly. The only problem now is that when I'm editing the view of the second type nodes, I can display the node that contains the location data, but I didn't find a way to make location-based manipulations. I can do them is the first type nodes and it will work, but what about location-based search? I would like this to be available also, and right now Drupal still doesn't recognize the location as belong to the second type node. Thanks, Daniel
On Wed, Aug 15, 2012 at 4:01 PM, Joel Willers joel.willers@sigler.comwrote:
Seems like a good solution to me. You can even make a View that will show in the list of potential locations only the locations that the user has made (a bit advanced, but all done through the UI).
Good luck!
Joel
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 7:55 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi Joel, First- thank you!
So if I undestand you correctly, I have one type that contain just the location and the title, and another which is my main type that contains all the information needed as well as a reference to the first type. But - I want every user to have its own locations list. So should I allow them to make a list of nodes of first content type?
On Wed, Aug 15, 2012 at 3:42 PM, Joel Willers joel.willers@sigler.com wrote:
If I understand your problem correctly, I think I'd make two content
types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead of
the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations.
I've managed to create a string field that allows the user to choose
from his list and contains the location ID.
The problem is that in this method Drupal doesn't recognize it as a
Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
- When the user create the node, he will choose from his list, but
Drupal will save it as it would save a node with new location.
- The data would be saved in the same method I'm using now (string
field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement
either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
Hi everyone, Any idea about the post below? Thanks! Daniel
On Wed, Aug 15, 2012 at 10:07 PM, daniel bareket danielbareket@gmail.comwrote:
Hi again, So- I've tried your suggestion, and it seems to work almost perfectly. The only problem now is that when I'm editing the view of the second type nodes, I can display the node that contains the location data, but I didn't find a way to make location-based manipulations. I can do them is the first type nodes and it will work, but what about location-based search? I would like this to be available also, and right now Drupal still doesn't recognize the location as belong to the second type node. Thanks, Daniel
On Wed, Aug 15, 2012 at 4:01 PM, Joel Willers joel.willers@sigler.comwrote:
Seems like a good solution to me. You can even make a View that will show in the list of potential locations only the locations that the user has made (a bit advanced, but all done through the UI).
Good luck!
Joel
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 7:55 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi Joel, First- thank you!
So if I undestand you correctly, I have one type that contain just the location and the title, and another which is my main type that contains all the information needed as well as a reference to the first type. But - I want every user to have its own locations list. So should I allow them to make a list of nodes of first content type?
On Wed, Aug 15, 2012 at 3:42 PM, Joel Willers joel.willers@sigler.com wrote:
If I understand your problem correctly, I think I'd make two content
types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead
of the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations.
I've managed to create a string field that allows the user to choose
from his list and contains the location ID.
The problem is that in this method Drupal doesn't recognize it as a
Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
- When the user create the node, he will choose from his list, but
Drupal will save it as it would save a node with new location.
- The data would be saved in the same method I'm using now (string
field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement
either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
I guess I don't fully understand your problem, but everything can be done with Relationships for selecting the correct node, and a Proximity filter should help. I've had to do some playing around with the proximity filter, but it worked for me for D6 in the past. Never tried in any others. Just read the README and you should be fine.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Monday, August 20, 2012 7:39 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi everyone, Any idea about the post below? Thanks! Daniel On Wed, Aug 15, 2012 at 10:07 PM, daniel bareket danielbareket@gmail.com wrote: Hi again, So- I've tried your suggestion, and it seems to work almost perfectly. The only problem now is that when I'm editing the view of the second type nodes, I can display the node that contains the location data, but I didn't find a way to make location-based manipulations. I can do them is the first type nodes and it will work, but what about location-based search? I would like this to be available also, and right now Drupal still doesn't recognize the location as belong to the second type node. Thanks, Daniel
On Wed, Aug 15, 2012 at 4:01 PM, Joel Willers joel.willers@sigler.com wrote: Seems like a good solution to me. You can even make a View that will show in the list of potential locations only the locations that the user has made (a bit advanced, but all done through the UI).
Good luck!
Joel
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 7:55 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi Joel, First- thank you!
So if I undestand you correctly, I have one type that contain just the location and the title, and another which is my main type that contains all the information needed as well as a reference to the first type. But - I want every user to have its own locations list. So should I allow them to make a list of nodes of first content type?
On Wed, Aug 15, 2012 at 3:42 PM, Joel Willers joel.willers@sigler.com wrote:
If I understand your problem correctly, I think I'd make two content types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead of the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations. I've managed to create a string field that allows the user to choose from his list and contains the location ID. The problem is that in this method Drupal doesn't recognize it as a Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
- When the user create the node, he will choose from his list, but Drupal will save it as it would save a node with new location.
- The data would be saved in the same method I'm using now (string field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
Proximity filter works only on the Location node, it doesn't work for the main node even though I have connected them using relationship. I am also trying to do much simpler version: display the city of the main node, but it still doesn't display anything. Maybe I did it wrong? In the main node I created a node - reference field and connected it to a Location node. Thanks!
On Mon, Aug 20, 2012 at 3:58 PM, Joel Willers joel.willers@sigler.comwrote:
I guess I don't fully understand your problem, but everything can be done with Relationships for selecting the correct node, and a Proximity filter should help. I've had to do some playing around with the proximity filter, but it worked for me for D6 in the past. Never tried in any others. Just read the README and you should be fine.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Monday, August 20, 2012 7:39 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi everyone, Any idea about the post below? Thanks! Daniel On Wed, Aug 15, 2012 at 10:07 PM, daniel bareket danielbareket@gmail.com wrote: Hi again, So- I've tried your suggestion, and it seems to work almost perfectly. The only problem now is that when I'm editing the view of the second type nodes, I can display the node that contains the location data, but I didn't find a way to make location-based manipulations. I can do them is the first type nodes and it will work, but what about location-based search? I would like this to be available also, and right now Drupal still doesn't recognize the location as belong to the second type node. Thanks, Daniel
On Wed, Aug 15, 2012 at 4:01 PM, Joel Willers joel.willers@sigler.com wrote: Seems like a good solution to me. You can even make a View that will show in the list of potential locations only the locations that the user has made (a bit advanced, but all done through the UI).
Good luck!
Joel
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 7:55 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi Joel, First- thank you!
So if I undestand you correctly, I have one type that contain just the location and the title, and another which is my main type that contains all the information needed as well as a reference to the first type. But - I want every user to have its own locations list. So should I allow them to make a list of nodes of first content type?
On Wed, Aug 15, 2012 at 3:42 PM, Joel Willers joel.willers@sigler.com wrote:
If I understand your problem correctly, I think I'd make two content
types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead of
the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations.
I've managed to create a string field that allows the user to choose
from his list and contains the location ID.
The problem is that in this method Drupal doesn't recognize it as a
Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
- When the user create the node, he will choose from his list, but
Drupal will save it as it would save a node with new location.
- The data would be saved in the same method I'm using now (string
field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement
either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
You need to create the Relationship, then make sure when you create the field or filter that you apply that relationship.
You can test to see if it's working by filtering to a specific node with several related nodes. When you add Node Title to the Views Field list, it should have ONE item, then add the relationship and POOF! multiples of the same. Then you can add Node Title again, apply the relationship, and you'll see the titles of the others.
Let's say we have the following: Node 1 Related to: Node A Node B Node C
First round (no relationship): Node 1
Second round (added relationship): Node 1 Node 1 Node 1
Third round (added related Node Title)
Node 1 Node A
Node 1 Node B
Node 1 Node C
Hopefully I'm not over explaining something you already know. Hope that helps,
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Monday, August 20, 2012 8:09 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Proximity filter works only on the Location node, it doesn't work for the main node even though I have connected them using relationship. I am also trying to do much simpler version: display the city of the main node, but it still doesn't display anything. Maybe I did it wrong? In the main node I created a node - reference field and connected it to a Location node. Thanks! On Mon, Aug 20, 2012 at 3:58 PM, Joel Willers joel.willers@sigler.com wrote: I guess I don't fully understand your problem, but everything can be done with Relationships for selecting the correct node, and a Proximity filter should help. I've had to do some playing around with the proximity filter, but it worked for me for D6 in the past. Never tried in any others. Just read the README and you should be fine.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Monday, August 20, 2012 7:39 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi everyone, Any idea about the post below? Thanks! Daniel On Wed, Aug 15, 2012 at 10:07 PM, daniel bareket danielbareket@gmail.com wrote: Hi again, So- I've tried your suggestion, and it seems to work almost perfectly. The only problem now is that when I'm editing the view of the second type nodes, I can display the node that contains the location data, but I didn't find a way to make location-based manipulations. I can do them is the first type nodes and it will work, but what about location-based search? I would like this to be available also, and right now Drupal still doesn't recognize the location as belong to the second type node. Thanks, Daniel
On Wed, Aug 15, 2012 at 4:01 PM, Joel Willers joel.willers@sigler.com wrote: Seems like a good solution to me. You can even make a View that will show in the list of potential locations only the locations that the user has made (a bit advanced, but all done through the UI).
Good luck!
Joel
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 7:55 AM To: support@drupal.org Subject: Re: [support] Help in using Location module
Hi Joel, First- thank you!
So if I undestand you correctly, I have one type that contain just the location and the title, and another which is my main type that contains all the information needed as well as a reference to the first type. But - I want every user to have its own locations list. So should I allow them to make a list of nodes of first content type?
On Wed, Aug 15, 2012 at 3:42 PM, Joel Willers joel.willers@sigler.com wrote:
If I understand your problem correctly, I think I'd make two content types, one with a location and a title, and the other with a Reference to the first. Then you can get all the location info you want with no tweaking/programming. Plus, you can manage the locations they can choose easily. You could use taxonomy to sort them, if you wish, or even use access controls to limit them by role.
Joel
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of daniel bareket Sent: Wednesday, August 15, 2012 4:15 AM To: support@drupal.org Subject: [support] Help in using Location module
Hi everyone, I have a content type that should have a Location field. But, instead of the user filling the location for every item, I would like him to only choose a location from his own list of pre-defined locations. I've managed to create a string field that allows the user to choose from his list and contains the location ID. The problem is that in this method Drupal doesn't recognize it as a Location-type field, and therefore all the advanced options like displaing on a map are not available.
I've thought about two methods to solve it:
- When the user create the node, he will choose from his list, but Drupal will save it as it would save a node with new location.
- The data would be saved in the same method I'm using now (string field with the ID), but somehow I will tell Drupal to recognize it as a location.
Not really sure which one is better, and I don't know how to implement either one.
My Drupal version is 6.
I hope it was clear enough. If not - I will try to explain again. Any help would be appreciated. Thanks a lot, Daniel
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ] -- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-
daniel bareket -
Joel Willers