Get Location Taxonomize to work all entities, not just nodes [#1541310]

I've tried every combination I can think of - Location (documented not working with profile2), Location CCK (documented not working with taxonomize), Getlocation, AddressField. I've tried 7.x-2.3 as well as the dev version.
taxonomize only seems to work when the various fields are attached to a content type, and doesn't seem to work when part of profile2 or the user profile. I need to define an address for a user that builds a taxonomy hierarchy (Country -> State/Province -> City), but nothing I do is working. Does anyone have a workaround or solution. or am I missing something? All the fields are flagged "Taxonomize locations from this field using Location Taxonomize"

Comments

Comment #1

danon1981 commented 3 September 2012 at 01:12

subscribing

Comment #2

wOOge commented 3 September 2012 at 17:13

Does this module work when the Address Field is inside a core Profile?
For example, each of my users can set their address in their own core profile settings (using an AF Field).

When a user saves their location (or when I choose bulk update from LT's configuration) it reports back that 0 addresses were processed.

Any more people having this issue?

Location Taxonomize: 7.x-2.4 (June 4, 2012)
Address Field: 7.x-1.0-beta3 (May 29, 2012)
Drupal: 7.15

Comment #3

Stefan Haas commented 9 September 2012 at 22:01

I have the same problem. I tried to get to work this on the core user profile with adress field module.

Comment #4

goron commented 10 September 2012 at 17:48

Title:	Not working with profile2 or user profile	» Get Location Taxonomize to work all entities, not just nodes
Version:	7.x-2.3	» 7.x-2.x-dev
Category:	support	» feature

I can confirm that parts of LT are hardcoded to work only with nodes and not other entity types. This is the case because at the time I was writing it there were still some bugs with the core entity API that were making it difficult to implement for all entities. Because of this, the whole module is restricted to nodes. This can certainly be fixed, but it'll require some work. My time currently is relatively limited, so it'll be a little while before I can get to it.

Patches are welcome, as always.

Comment #5

wOOge commented 13 September 2012 at 16:00

Thanks for the clarification @goron

Comment #6

Golem07 commented 13 September 2012 at 18:58

I too am in need for this to work with Profile 2 and would gladly chip in if this could help in any way.

Comment #7

Chaz Cheadle commented 19 September 2012 at 19:44

Subscribing as well.
I have AddressFields in a Field Collection, which I believe faces the same problem as the Profile2 issue.
We are creating a directory and members can have multiple 'contacts' that are built on fieldcollections of AddressFields and other data. I wonder if custom code for digging into Profile2 and fieldcollections(1 level deep) is needed as the depth/configuration of each is too different, or if parsing through a node's entities can be done and a check for a 'addressfield' entity type can be done- just thinking out loud.

Chaz

Comment #8

danon1981 commented 17 October 2012 at 12:19

Sub for field collection situation. Also facing the issues with getting address taxonomy data from a field collection. Also tried to place taxonomy field and address field inside same collection but without any luck

Comment #9

stevenx commented 12 February 2013 at 16:10

What shall I look for to find all the places in code where that happens to be hardcoded?
I need it to run with USERs instead of nodes. Nodes work great.

thx