Is it possible to develop integration with the PURL module to pass the context of location from page to page? I wouldn't know how.

Comments

ademarco’s picture

That's might be interesting: to which kind of use case you would apply such an integration? Could you give me some examples?

Adam S’s picture

I was just wondering how to do this? http://www.examiner.com/minneapolis. Here the user location is set in a variable and the location is a taxonomy term. I though it might be one step better to geocode each node and show all the content in relation to where the user location is on a map. Currently every time the user searches for something Google services needs to be called.

Also with Context module there is no problem sending any node variable to Views as an argument using context_set() with nodeapi and then using context_get() within the arg->provide default arg-> PHP code in Views. How do I use the WKT or lat & long fields in a node so that I can pass location as an argument instead using a static node in the filters provided by Proximity module? (see http://drupal.org/project/views_arg_context)

Let's say that the website shows farms and each farm is a node with a location. I want to show all the markets that are within 200 miles of that farm. How do I pass the farms location to Views so that all the markets within the proximity are shown in a side block? Then best I can do now is show the closest x number using the Proximity modules sort.

Adam S’s picture

What I was able to do was hack the openlayers_proximity/views/openlayers_proximity_handler_filter.inc file. I removed the form that allowed a node to be set as the center of the proximity filter and replaced it with a context variable that contained parts of the $node variable based on context. Now I have a big map on each node that shows the all the other nodes that are in proximity. Cool beans.

I'm including screen images of my proof of concept.