After testing the content type import on three different sites Advanced Profile Kit should not have a generic field named location as it collides with the Location Module. The problem is that it also is enabled in CCK and the names conflict. So,
1. Auto creation of userprofile content type does not occur.
2. When you try to import the content type it will return errors regarding the location module.
Suggestion changing the filed name to my location etc may help negate the conflict.

Comments

vm’s picture

vm commented

or one could integrate location.module, no?

I suppose a field name change is easiest but when adding location.module wouldn't that then supply two location fields?

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Category: bug » task

Location as a field on the node type is old... It came from my site over 2 years ago. The fact that location apparantly can't deal if there is a field named location would be a bug in location, not a bug in APK. That said, APK really doesn't make use of that location field and the capabilities of user mapping, etc, from more advanced user locations that have happened since then make it even less useful to have a single text field on there. So I'm fine with taking it out. Actual integration built into APK I don't know about. There's already an integration with Author Pane... Beyond that, I'm not sure what would be needed. I'm open for suggestions but hesitant to be putting in too much given that I don't use user location myself and that runs into problems with adaquate testing.

Michelle

vm’s picture

vm commented

+1 for removal. Those using location won't get a naming conflict and those who want a location field can add one manually if not using location.module.

venusrising’s picture

venusrising commented

I just posted the info above as I re-created the issue on another site and did notice the crazy message from location when trying to dump a fresh profile in. I looked around a bit and figured it had to be GMAP/Location using generic location and not liking the filed called location in CCK. I figured that since I was easily deleted the location field in APK and the error was gone it would be easier to alter it to something like mylocation since there were not too many occurrences while I did see quite a few in location and it being a three part demon might be harder to mess with. In any case it does look nice in the author_pane.

venusrising’s picture

venusrising commented

Not sure if this will help anyone but Weird, I never got an update notification for the stable rc1 build of location but it fixes the issue of content profile creation (with content profile content at least.) That was a first step at least. http://drupal.org/project/location

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Oh, yeah, it definitely makes more sense to take the field out of APK than to get Location to change its naming. :)

Michelle

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Active » Closed (duplicate)

Merge with #575324: Revamp uprofile.inc