Answers.Body: <p>I have also seen this problem, and fixed it. It's nothing to do with CiviCRM at all - it's a recent change made by Google regarding their API and your authorisation to use it.  Existing users seem to be OK, but new users (ie. one of my clients) or maybe even new maps seem to be affected.  You should review your  authorisation to use the Google API for your domain.  It's a slightly confusing situation because it appears that you don't need to enter your API key on Civi anymore, but you do need to be authorised by Google.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-05T18:57:28.200Z
Answers.LastActivityDate: 2016-11-05T18:57:28.200Z
Answers.UserDisplayName: Andy Clark
Answers.Body: <p>Same problem here with a 4.7.12. I workarounded marking <code>Override automatic geocoding</code> and setting <code>latitud</code> and <code>longitud</code> coordinates manually.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-06-16T15:38:27.470Z
Answers.LastActivityDate: 2017-06-16T15:43:59.100Z
Answers.LastEditDate: 2017-06-16T15:43:59.100Z
Answers.UserDisplayName: Francesc Bassas i Bullich
Body: <p>I have just upgraded our CiviCRM install to 4.7.13. When creating a new event and selecting all relevant options, the Google Map is not displayed. This IS displayed when viewing other active and older events.</p>
  
  <p>We have been using a custom .tpl file, but even after disabling the tpl and clearing the cache(s) we are still facing the same issue.</p>
  
  <p>Any ideas what might be going on here?</p>
  
  <p>For testing we are using the same stored address. The existing, pre-upgrade event has the following values:</p>
  
  <pre><code>{$event.is_map} = 1
  {$config-&gt;mapProvider} = Google
  {$location.address.1.geo_code_1} = 56.0797664
  {$location.address.1.city} = Dunfermline
  {$location.address.1.state_province} = NULL
  </code></pre>
  
  <p>The map is displayed.</p>
  
  <p>A new event, post-upgrade, with exactly the same settings has the following:</p>
  
  <pre><code>{$event.is_map} = 1
  {$config-&gt;mapProvider} = Google
  {$location.address.1.geo_code_1} = NULL
  {$location.address.1.city} = Dunfermline
  {$location.address.1.state_province} = NULL
  </code></pre>
  
  <p>The map is missing.</p>
  
  <p>When we open the location information on the old event and save, the map fails to work ?!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-11-05T14:24:53.327Z
Comments.Text: *The same stored address* does that mean the same record (thus a record in civicrm_addresses), or the same entity (the same combination of address fields, but stored in a different record in the database)?
Comments.UserDisplayName: Kainuk - CiviCooP
Tags: <civievent><location><map>
Title: Google Map not displaying on new events
ThreadText: # Google Map not displaying on new events
  
  (Asked by: username_0 on 2016-11-04)
  
  I have just upgraded our CiviCRM install to 4.7.13. When creating a new event and selecting all relevant options, the Google Map is not displayed. This IS displayed when viewing other active and older events.
  
  We have been using a custom .tpl file, but even after disabling the tpl and clearing the cache(s) we are still facing the same issue.
  
  Any ideas what might be going on here?
  
  For testing we are using the same stored address. The existing, pre-upgrade event has the following values:
  
  ```
  {$event.is_map} = 1
  {$config->mapProvider} = Google
  {$location.address.1.geo_code_1} = 56.0797664
  {$location.address.1.city} = Dunfermline
  {$location.address.1.state_province} = NULL
  
  ```
  
  The map is displayed.
  
  A new event, post-upgrade, with exactly the same settings has the following:
  
  ```
  {$event.is_map} = 1
  {$config->mapProvider} = Google
  {$location.address.1.geo_code_1} = NULL
  {$location.address.1.city} = Dunfermline
  {$location.address.1.state_province} = NULL
  
  ```
  
  The map is missing.
  
  When we open the location information on the old event and save, the map fails to work ?!
  
  **Tags:** civievent, location, map
  
  > **Comments:**
  > **username_1**: *The same stored address* does that mean the same record (thus a record in civicrm_addresses), or the same entity (the same combination of address fields, but stored in a different record in the database)?  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-11-05. Score: 2 | Accepted answer
  
  I have also seen this problem, and fixed it. It's nothing to do with CiviCRM at all - it's a recent change made by Google regarding their API and your authorisation to use it. Existing users seem to be OK, but new users (ie. one of my clients) or maybe even new maps seem to be affected. You should review your authorisation to use the Google API for your domain. It's a slightly confusing situation because it appears that you don't need to enter your API key on Civi anymore, but you do need to be authorised by Google.
  
  
  ---
  
  ### Answer by username_3 on 2017-06-16. Score: 0
  
  Same problem here with a 4.7.12. I workarounded marking `Override automatic geocoding` and setting `latitud` and `longitud` coordinates manually.
  
  
  ---
  
  