Answers.Body: <p>As discussed in CRM-16499, the bug involves processing file relative-paths and absolute-paths on Windows. I reproduced the bug with D7 and XAMPP for Windows. There's a <a href="https://github.com/civicrm/civicrm-core/pull/5863">pending fix</a> (<a href="https://patch-diff.githubusercontent.com/raw/civicrm/civicrm-core/pull/5863.patch">.patch</a>). </p>
  
  <p>It <em>might</em> get merged before tomorrow's release (4.6.3); otherwise, it'll go out with 4.6.4.</p>
  
  <p>Note: For general advice on how to interpret/evaluate pending patches, see <a href="http://wiki.civicrm.org/confluence/display/CRM/Verify+a+patch">http://wiki.civicrm.org/confluence/display/CRM/Verify+a+patch</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-20T04:42:59.203Z
Answers.LastActivityDate: 2015-05-20T04:42:59.203Z
Answers.UserDisplayName: Tim Otten
Answers.Body: <p>Looks like you've found a bug.</p>
  
  <p>It's currently being worked on by the core team, you can follow progress at</p>
  
  <p><a href="https://issues.civicrm.org/jira/browse/CRM-16499" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-16499</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-02T21:29:28.560Z
Answers.Text: Patch appears to have worked.
Answers.UserDisplayName: pmoz
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-19T21:26:32.957Z
Answers.LastActivityDate: 2015-05-19T21:26:32.957Z
Answers.UserDisplayName: Coleman
Body: <p>I recently installed CiviCRM 4.6.2 in our multisite Drupal 7 environment, running on IIS 8. I have CiviCRM 4.3.2 running on a Drupal 6 base without any issues on the same server; my plan is to migrate the D6 install and most of the data (contacts, etc) to D7. </p>
  
  <p>Installation and configuration of CiviCRM went fine, as did importing contacts. However, I'm currently stuck on an issue that appears to have something to do with AngularJS and Windows/IIS paths, though I can't say that for sure. </p>
  
  <p>When I go to Mailings -> New Mailing, it hangs - all it says on the page is "Initializing..." In Chrome's console, I see this error:</p>
  
  <pre><code>TypeError: a.headers is not a function
    at n (angular.js:9720)
    at angular.js:13248
    at n.$get.n.$eval (angular.js:14466)
    at n.$get.n.$digest (angular.js:14282)
    at n.$get.n.$apply (angular.js:14571)
    at l (angular.js:9698)
    at M (angular.js:9888)
    at XMLHttpRequest.F.onload (angular.js:9829)
  </code></pre>
  
  <p>In Drupal's watchdog log, I get this error (identifying path info changed):</p>
  
  <pre><code>LOCATION    https://www.fake.com/civicrm/ajax/angular-modules?l=en_US&amp;r=fE7WM
  
  REFERRER    https://www.fake.com/civicrm/a/
  
  MESSAGE     Warning: file_get_contents(E:\webroot\drupalroot\sites\all\modules\civicrm/ang/crmMailingAB/E:\webroot\drupalroot\sites\all\modules\civicrm/ang/crmMailingAB\EditCtrl/report.html): failed to open stream: Invalid argument in Civi\Angular\Manager-&gt;getPartials() (line 203 of E:\webroot\drupalroot\sites\all\modules\civicrm\Civi\Angular\Manager.php).
  </code></pre>
  
  <p>It definitely looks to me like AngularJS is getting confused by Windows paths, but I'm not 100% sure that that's what's going on, nor how to fix it if I'm right.</p>
  
Tags: <drupal>
Title: AngularJS issues with Drupal 7 + CiviCRM
ThreadText: # AngularJS issues with Drupal 7 + CiviCRM
  
  (Asked by: username_0 on 2015-05-12)
  
  I recently installed CiviCRM 4.6.2 in our multisite Drupal 7 environment, running on IIS 8. I have CiviCRM 4.3.2 running on a Drupal 6 base without any issues on the same server; my plan is to migrate the D6 install and most of the data (contacts, etc) to D7.
  
  Installation and configuration of CiviCRM went fine, as did importing contacts. However, I'm currently stuck on an issue that appears to have something to do with AngularJS and Windows/IIS paths, though I can't say that for sure.
  
  When I go to Mailings -> New Mailing, it hangs - all it says on the page is "Initializing..." In Chrome's console, I see this error:
  
  ```
  TypeError: a.headers is not a function
    at n (angular.js:9720)
    at angular.js:13248
    at n.$get.n.$eval (angular.js:14466)
    at n.$get.n.$digest (angular.js:14282)
    at n.$get.n.$apply (angular.js:14571)
    at l (angular.js:9698)
    at M (angular.js:9888)
    at XMLHttpRequest.F.onload (angular.js:9829)
  
  ```
  
  In Drupal's watchdog log, I get this error (identifying path info changed):
  
  ```
  LOCATION    https://www.fake.com/civicrm/ajax/angular-modules?l=en_US&r=fE7WM
  
  REFERRER    https://www.fake.com/civicrm/a/
  
  MESSAGE     Warning: file_get_contents(E:\webroot\drupalroot\sites\all\modules\civicrm/ang/crmMailingAB/E:\webroot\drupalroot\sites\all\modules\civicrm/ang/crmMailingAB\EditCtrl/report.html): failed to open stream: Invalid argument in Civi\Angular\Manager->getPartials() (line 203 of E:\webroot\drupalroot\sites\all\modules\civicrm\Civi\Angular\Manager.php).
  
  ```
  
  It definitely looks to me like AngularJS is getting confused by Windows paths, but I'm not 100% sure that that's what's going on, nor how to fix it if I'm right.
  
  **Tags:** drupal
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-05-20. Score: 5
  
  As discussed in CRM-16499, the bug involves processing file relative-paths and absolute-paths on Windows. I reproduced the bug with D7 and XAMPP for Windows. There's a [pending fix](https://github.com/civicrm/civicrm-core/pull/5863) ([.patch](https://patch-diff.githubusercontent.com/raw/civicrm/civicrm-core/pull/5863.patch)).
  
  It *might* get merged before tomorrow's release (4.6.3); otherwise, it'll go out with 4.6.4.
  
  Note: For general advice on how to interpret/evaluate pending patches, see <http://wiki.civicrm.org/confluence/display/CRM/Verify+a+patch>
  
  
  ---
  
  ### Answer by username_2 on 2015-05-19. Score: 4
  
  Looks like you've found a bug.
  
  It's currently being worked on by the core team, you can follow progress at
  
  <https://issues.civicrm.org/jira/browse/CRM-16499>
  
  > **Comments:**
  > **username_3**: Patch appears to have worked.  
  
  ---
  
  