Answers.Body: <p>Aaahhhh!!!! I just noticed that this client's Drupal user ID was set to view the site with the default Garland theme whereas my Drupal user ID was set to view the site with the custom theme built for this site. I switched the client's Drupal user ID to use the custom theme, and now AJAX refreshes correctly. So, it appears Drupal Garland theme specific.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-16T14:10:06.133Z
Answers.LastActivityDate: 2015-05-16T14:10:06.133Z
Answers.UserDisplayName: Michael Lueck
Answers.Body: <p>It could be cached resources in their browser. Ask them to do a force-refresh (ctrl-shift-R in Chrome &amp; FF).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-07T02:34:55.837Z
Answers.LastActivityDate: 2015-05-07T02:34:55.837Z
Answers.UserDisplayName: Coleman
Answers.Body: <p>It appears to be specific to this client's computers verses our development computers. I have had success with Mozilla Firefox both in my native Linux, and also a Windows VM.</p>
  
  <p>However the client has attempted to connect from their Windows 7 computer with Google Chrome, Internet Explorer 11, and Mozilla Firefox. The problem is consistent across all these browsers. It appears to be a consistent AJAX issue for this client.</p>
  
  <p>The client installed Mozilla Firefox to debug this issue. Their preferred browser is Google Chrome... so definitely old cached files is not the answer.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-16T13:48:36.160Z
Answers.LastActivityDate: 2015-05-16T13:48:36.160Z
Answers.UserDisplayName: Michael Lueck
Answers.Body: <p>I suggest you start by going through the steps for <a href="http://forum.civicrm.org/index.php/topic,35850" rel="nofollow">troubleshooting javascript in CiviCRM</a>.  If that doesn't fix the problem, please edit the question to report back what data you've gathered from the process.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-05T13:43:20.090Z
Answers.LastActivityDate: 2015-05-05T13:43:20.090Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>We consult with CiviCRM powered by Drupal. Recently we upgraded one client who has CiviCRM powered by the latest Drupal 6 from 4.5.8 to 4.6.2. After the upgrade, they are unable to click between the various tabs of a CiviContact record. They have tried multiple different browser products from I believe their Windows based computer.</p>
  
  <p>Tabs are as follows on a particular CiviContact record:
      Summary
      Contributions 263
      Pledges 0
      Memberships 0
      Activities 61
      Events 7
      Relationships 0
      Groups 41
      Notes 2
      Tags 5
      Change Log 18</p>
  
  <p>Always the lower content area is stuck showing the Summary details.
  We see no troubles from Mozilla Firefox on Linux, or Google Chrome. I tried Chrome as they say that is their preferred browser.</p>
  
  <p>Some time ago I recall some AJAX code getting broken in a couple of CiviCRM upgrade on Drupal 6. Perhaps that has happened again. Though odd this time it is specific to the operating system of the browser, not a cross-platform break.</p>
  
  <p>Any other suggestions of information I might provide?</p>
  
  <p>I am thankful,
  Michael</p>
  
Tags: <drupal><upgrade><ajax>
Title: Upgrade from 4.5.8 to 4.6.2 killed View Contact Tabs
ThreadText: # Upgrade from 4.5.8 to 4.6.2 killed View Contact Tabs
  
  (Asked by: username_0 on 2015-05-05)
  
  We consult with CiviCRM powered by Drupal. Recently we upgraded one client who has CiviCRM powered by the latest Drupal 6 from 4.5.8 to 4.6.2. After the upgrade, they are unable to click between the various tabs of a CiviContact record. They have tried multiple different browser products from I believe their Windows based computer.
  
  Tabs are as follows on a particular CiviContact record:
  Summary
  Contributions 263
  Pledges 0
  Memberships 0
  Activities 61
  Events 7
  Relationships 0
  Groups 41
  Notes 2
  Tags 5
  Change Log 18
  
  Always the lower content area is stuck showing the Summary details.
  We see no troubles from Mozilla Firefox on Linux, or Google Chrome. I tried Chrome as they say that is their preferred browser.
  
  Some time ago I recall some AJAX code getting broken in a couple of CiviCRM upgrade on Drupal 6. Perhaps that has happened again. Though odd this time it is specific to the operating system of the browser, not a cross-platform break.
  
  Any other suggestions of information I might provide?
  
  I am thankful,
  Michael
  
  **Tags:** drupal, upgrade, ajax
  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_0 on 2015-05-16. Score: 2 | Accepted answer
  
  Aaahhhh!!!! I just noticed that this client's Drupal user ID was set to view the site with the default Garland theme whereas my Drupal user ID was set to view the site with the custom theme built for this site. I switched the client's Drupal user ID to use the custom theme, and now AJAX refreshes correctly. So, it appears Drupal Garland theme specific.
  
  
  ---
  
  ### Answer by username_1 on 2015-05-07. Score: 0
  
  It could be cached resources in their browser. Ask them to do a force-refresh (ctrl-shift-R in Chrome & FF).
  
  
  ---
  
  ### Answer by username_0 on 2015-05-16. Score: 0
  
  It appears to be specific to this client's computers verses our development computers. I have had success with Mozilla Firefox both in my native Linux, and also a Windows VM.
  
  However the client has attempted to connect from their Windows 7 computer with Google Chrome, Internet Explorer 11, and Mozilla Firefox. The problem is consistent across all these browsers. It appears to be a consistent AJAX issue for this client.
  
  The client installed Mozilla Firefox to debug this issue. Their preferred browser is Google Chrome... so definitely old cached files is not the answer.
  
  
  ---
  
  ### Answer by username_2 on 2015-05-05. Score: 0
  
  I suggest you start by going through the steps for [troubleshooting javascript in CiviCRM](http://forum.civicrm.org/index.php/topic,35850). If that doesn't fix the problem, please edit the question to report back what data you've gathered from the process.
  
  
  ---
  
  