Answers.Body: <p>This is usually a local issue; if you clear your browser's cookies the error should go away.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-16T16:51:52.660Z
Answers.LastActivityDate: 2015-06-16T16:51:52.660Z
Answers.UserDisplayName: Nicholai
Body: <p>I was testing a contribution form today and noticed an error in the console on the thank you page. I'm guessing it is related to the Google Plus portion of the "Help spread the word" section, but am not certain. The site does also have a Google Plus URL set as rel="Publisher" using the Metatag module (Drupal).</p>
  
  <p>If I leave the page open and the console open, this error just keeps recurring again and again:</p>
  
  <p><strong>Refused to display...in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'</strong></p>
  
  <p><img src="https://i.sstatic.net/WkKY6.jpg" alt="Refused to display...in a frame because it set &#39;X-Frame-Options&#39; to &#39;SAMEORIGIN&#39;"></p>
  
  <p>What would cause this?</p>
  
Tags: <civicontribute><social-media>
Title: Console error with Google Plus and "Help spread the word"
ThreadText: # Console error with Google Plus and "Help spread the word"
  
  (Asked by: username_0 on 2015-06-16)
  
  I was testing a contribution form today and noticed an error in the console on the thank you page. I'm guessing it is related to the Google Plus portion of the "Help spread the word" section, but am not certain. The site does also have a Google Plus URL set as rel="Publisher" using the Metatag module (Drupal).
  
  If I leave the page open and the console open, this error just keeps recurring again and again:
  
  **Refused to display...in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'**
  
  ![Refused to display...in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'](https://i.sstatic.net/WkKY6.jpg)
  
  What would cause this?
  
  **Tags:** civicontribute, social-media
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-06-16. Score: 2 | Accepted answer
  
  This is usually a local issue; if you clear your browser's cookies the error should go away.
  
  
  ---
  
  