Answers.Body: <p>It turns out it was civicrm file permissions (in sites/all) conflicting with my server's PHP access settings.</p>
  
  <p>My server dictates that if any part of a path is group writable, php file access will be denied. So I (well, my hired support person because I got desperate) went and set the directories involved to permission 755, and the file to permission 644 (civicrm/extern/soap.php).</p>
  
  <p>My secondary problems with cron (civicrm/bin/cron.php) and not being able to browse for images in civimail (civicrm/packages/kcfinder/*) were fixed by following the same logic.</p>
  
  <p>I'm still not sure why this was triggered by an upgrade from 4.7.18 to 4.7.19. I must have made a misstep during file copying. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-26T18:32:36.100Z
Answers.Text: Just to tag on here, this happened to us as well, but we noticed it because we couldn't upload images in CiviMail, and click tracking was broken in CiviMail as well. Changing permissions on the files solved it.
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-26T18:12:09.840Z
Answers.Text: We also had cron job failing to run after upgrades (to 7.4.24 on Wordpress). Copying the url from the wget command and plugging in to browser bought up the message "Incorrect file/directory permissions: Above 755. In order files to be processed by the webserver, their permissions have to be equal or below 755." Changing permissions on cron.php from 664 to 664 seemed to sort it.
Answers.UserDisplayName: Eric Booth
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-16T20:51:14.283Z
Answers.LastActivityDate: 2017-05-16T20:51:14.283Z
Answers.UserDisplayName: Eric H
Body: <p>I recently upgraded from 4.7.18 to 4.7.19 (under Drupal 7.54) and now CiviSMTP (as well as my browser) gets Drupal's "Page not found" page when trying to get to my soap.php file.</p>
  
  <p><code>Page not found
  The requested page "/sites/all/modules/civicrm/extern/soap.php" could not be found.
  </code></p>
  
  <p>I've confirmed the file is in place, I'm using the default Drupal .htaccess file, file permissions seem to be at their defaults (AFAIK), and I'm out of ideas. My cron jobs are also not running, but I figure there's a common cause.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-16T10:34:48.537Z
Comments.Text: I assume CiviCRM is correctly enabled? seems very strange
Comments.UserDisplayName: Seamus Lee
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-16T14:43:14.910Z
Comments.Text: As far as Drupal modules go? Yes.
Comments.UserDisplayName: Eric H
Tags: <civimail><soap>
Title: Upgrading from 4.7.18 to 4.7.19 breaks soap
ThreadText: # Upgrading from 4.7.18 to 4.7.19 breaks soap
  
  (Asked by: username_0 on 2017-05-12)
  
  I recently upgraded from 4.7.18 to 4.7.19 (under Drupal 7.54) and now CiviSMTP (as well as my browser) gets Drupal's "Page not found" page when trying to get to my soap.php file.
  
  `Page not found
  The requested page "/sites/all/modules/civicrm/extern/soap.php" could not be found.`
  
  I've confirmed the file is in place, I'm using the default Drupal .htaccess file, file permissions seem to be at their defaults (AFAIK), and I'm out of ideas. My cron jobs are also not running, but I figure there's a common cause.
  
  **Tags:** civimail, soap
  
  > **Comments:**
  > **username_1**: I assume CiviCRM is correctly enabled? seems very strange  
  > **username_0**: As far as Drupal modules go? Yes.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-05-16. Score: 3 | Accepted answer
  
  It turns out it was civicrm file permissions (in sites/all) conflicting with my server's PHP access settings.
  
  My server dictates that if any part of a path is group writable, php file access will be denied. So I (well, my hired support person because I got desperate) went and set the directories involved to permission 755, and the file to permission 644 (civicrm/extern/soap.php).
  
  My secondary problems with cron (civicrm/bin/cron.php) and not being able to browse for images in civimail (civicrm/packages/kcfinder/\*) were fixed by following the same logic.
  
  I'm still not sure why this was triggered by an upgrade from 4.7.18 to 4.7.19. I must have made a misstep during file copying.
  
  > **Comments:**
  > **username_2**: Just to tag on here, this happened to us as well, but we noticed it because we couldn't upload images in CiviMail, and click tracking was broken in CiviMail as well. Changing permissions on the files solved it.  
  > **username_3**: We also had cron job failing to run after upgrades (to 7.4.24 on Wordpress). Copying the url from the wget command and plugging in to browser bought up the message "Incorrect file/directory permissions: Above 755. In order files to be processed by the webserver, their permissions have to be equal or below 755." Changing permissions on cron.php from 664 to 664 seemed to sort it.  
  
  ---
  
  