Views 3.x incompatible with Location CCK, views or location problem?

That's probably a location module issue.

I have the same problem!
I updated to the latest views. The error occurs since the update.

same issue here

wrapping in code tags

I removed all Relationships with Location and added the fields without a relationship. This solved the problem.

Ok... I have this problem too.. I have it loading again. However, not in a way that will work systemically. I do want, however, to share what I have done just in case it helps.

I added the column lid to the content_field_location table. Then set the values in that column equal to the values in the lid column. Now everything is working again. I just can't do it this way because I don't believe the system will keep my column up to date.

Hi there,

I was having the same problem (using views-6.x.-3.0-rc1 and location-6.x.-3.x-dev Version of November 4th). As I understand this is caused by the location module not providing views with the correct information for the join defintions due to some changes in the views api.

Because my knowledge of the (updated) views api and the location module itself is rather poor I used a more or less quick and dirty hack to correct it (needed a solution fast). I used hook_views_query_alter to adjust the join definition for the location tables. In code this looks soemthing like this:

function MYMODULDE_views_query_alter(&$view, &$query) {
  if (!empty($query->table_queue['location_node_data_MYFIELD_NAME']['join']->left_field)) {
    $query->table_queue['location_node_data_MYFIELD_NAME']['join']->definition['left_field'] = 
    $query->table_queue['location_node_data_MYFIELD_NAME']['join']->left_field =
      'MYFIELD_NAME_lid';
  }
}

Not really beautiful but it works for now for me.

Cheers,
cossme

This patch should fix the issue. In the CCK definition it was telling views to use lid as the field as opposed to the field_alias

#8 works for me, using Location 3.x-dev and Views 3.0-rc2

thank you, arcaneadam - so glad i didn't have to track this down myself.
#8 works for me, and it's a one-liner of a very obvious bug - let's get it in!

Does this patch break compatibility with 6.x-2.x?

If so, I'd like to figure out the best way to maintain compatibility with both views 6.x-2.x and views 6.x-3.x before committing this patch to location's 6.x-3.x branch.

I don't think this is an issue with views. It's an issue more with how Location and CCk define the field with views. All it does is ensure that the DB field views is querying against is the correct field.

That being said. I agree it would be a good idea for someone to test vs. views 2 to ensure it still works.

The patch works flawlessly and should be commited soon. Using Views 3 is very common now.

Don't forget to flush the cache, because views schemas are cached.

The patch works great with views 3
please commit

#8 patch worked for me too. Is there a reason it hasn't been committed yet?

Works here as well. If there was a step higher than RTBC I'd mark it.

RE #11, I hate to say it, but perhaps we need to make two versions of the Location module, one for views 2 and one for views 3 and create warning messages if they're out of sync.

#8 works for me with views-6.x-3.x

postponed before tests fix
#1931088: [META] Fixing tests

postponed before tests fix
#1931088: [META] Fixing tests

removed redundant link

tests fixed #1931088: [META] Fixing tests
lets go

#8 commited pushed to 6.x-3.x
thanks!