Location Module issues.

This came up at today’s Drupal Group meeting when Adam was talking about the Loction module - http://drupal.org/project/location

The module allows the addition of a location to a node or a user - this gets added to the content type’s add/edit form as a section with the required/allowed location fields like address, city, state, etc.

But the module also can add location data to a node via CCK fields .  These fields are added just like other CCK fields - email, web address, etc. - in a content type’s “Manage Fields” section.

However, the ‘regular’ location function and the CCK location fields do not play well together.  In my example I wanted to create a content type for events.  They happen at a physical location, which I want to place on a map, but they also have information about the contact person for the event that could include their address, which I don’t want to place on a map.  So I used the ‘regular’ location for the event and the CCK fields for the contact person. 

This fails because you can’t use both methods for the same content type.  When you enter data, it does not get added to the DB correctly or it gets deleted, I’m not quite sure which.  The issue is mentioned on the module’s d.o page, but contrary to what is written is not in the module’s INSTALL.txt file.

You can find the issue at: http://drupal.org/node/1051582 .  I think a patch is being worked on, you can see info on: http://drupal.org/node/906968

One other issue with node locations, maps, and events - if you want a map of future events, make sure that your event content type requires an end date and that any views you create to display the map has a filter which only shows events whose end date is greater or equal  to the current date.