I am not sure where to report this bug. So I will start with node profile, but three other projects are involved. I am trying to import users using node profiles. Two of my node profiles are location enabled (home and work). But when I upload a csv file and attempt to match the fields, only one set of location fields are showing up in the drop down list.

When I drilled down to see what was happening ... this is what I discovered. The nodeprofile.inc file under the user_import module calls a function in node_import to get a list of available fields per nodeprofile type. The function in node_import however invokes its own call to the include files in its own subdirectory. All fine and good till location.inc is called where it sends back a set of location fields for each node profile type. The problem comes from the naming of the location fields being the same for each call - which means the second set called overwrites the first set called.

If this were a simple node import, it would simply mean that one could only import a single location, but since these are node profiles during a user import, we really do need to distinguish between locations on a per node profile type basis.

So I am not sure where the change needs to be made: node profile, user import, node import or location.

I hope this explanation makes sense ... I am thinking that it would be very helpful if the location fields were somehow tagged with their content type name instead of 'node_import_location_'. $field . But then maybe there is a better way out of this conundrum.

Katrina

--

www.ambereyes.net

Comments

DiJae’s picture

Title: Missing location fields within node profiles during user import » D

Did someone solve this problem. I'm trying to import node_profiles with user_import and the only location fields available are latitude, longitude and country. I'm missing street, postcode, additional...

ambereyes’s picture

Title: D » Missing location fields within node profiles during user import

Title was changed erroneously.