I mentioned this in another issue, but this is a whole different issue, so I'm opening a separate task thread.
Bug report:
The GMap doesn't display on user Profile2.
How to recreate this bug:
Modules: Profile 2, Location, CCK location, Gmap
Add a location field to users' Profile2. Enter their location (Country, City, Address etc). These are pretty much the standard steps of how you would normally use the Location and GMap modules for Nodes.
If you set the display to "Address only" -> it will display the Address as a text on user's profile (no problem).
If you set the display to a "Map", or anything involving a GMap, then it will display nothing!!!
I'm setting this to "critical" because displaying a Map on user profile is a pretty standard feature in contemporary websites, like directories.
Comments
Comment #1
fagoThis is not critical for the module to function. Also, it's most likely a bug in gmap not profile2.
Comment #2
johnvDid you find a solution already? Please upgrade to latest version.
Then, try if the field is shown outside the Profiel (directly on the user (or whatever) entity), to exclude the influence of Profile2.
Comment #3
johnvSee also #1766236: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'latitude' in 'field list'
Comment #4
coolhandlukek2 commented+1 - I am having this problem too (seems fairly critical to me)
Comment #5
dman commentedSo far I've found references to the same symptoms being reported in views using 'entities' not nodes.
So far taxonomy, media entity, and here profile. Each of these is similar in that they have partial views support, but not as much as 'nodes' traditionally did.
#1927726: Column not found error creating Views map of taxonomy terms (cck_location field attached to an entity not usable in views)
So it's location.module and/or gmap.module, but probably not profile.module specifically.
What is most painful lis that on failure, gmap view returns just blank, with no errors or logs. Even 'no data from view available' would have helped, as I spent ages looking for javascript errors or Google API changes and version conflicts.