Closed (duplicate)
Project:
Profile 2
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Mar 2011 at 04:09 UTC
Updated:
15 Feb 2013 at 11:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
kevinquillen commentedI have added the Location field to a simple Profile2 type. While the fields display on the form, the data is not saved (no location in the database). When the page reloads after saving, the fields are clear.
Comment #2
kevinquillen commentedIs there no resolve to this? The data just does not save.
Comment #3
kevinquillen commentedComment #4
Terko commentedI have the same problem, subscribe.
Comment #5
kevinquillen commentedThere is actually a patch for this from the Location threads. Trying to find the link..
Comment #6
Adam S commentededit: I take back everything I said about having luck with OpenLayers and Profile2. For some reason, OpenLayers and/or Views is using Reminents of Node API in Drupal 7 which doesn't help working with the Entity API causing quite a few errors. I'm sure that this problem is most likely systemic and will not be able to be solved until there is some agreement about Drupal's API's which will not happen if at all until Drupal 8. *sigh*
Comment #7
westbywest commentedHere is the comment on the Location CCK module with the patch:
http://drupal.org/node/1064666#comment-4297472
For D7.7, profile2 7.x-1.0, and location 7.x-3.x-dev, I can confirm that this does allow saving of 1 location field in a profile2 profile (didn't yet try multiple locations).
However, the location is not displayed when viewing the user profile. You could write a custom user.tpl in your theme to work-around, but the patch isn't complete yet.
Comment #8
fagook, so the issue is #1064666: Location CCK not saving for entities other than nodes
let's leave this open (@postponed) until it's fixed in location, so others can find it.
Comment #9
raulmuroc commentedOne year. Nothing else. It can be closed.