Answers.Body: <p>The answer now is to upgrade from 4.7.1 to 4.7.4 or better.
  Apparently a number of paypal processes were corrected after this and other posts on civicrm.stackexchange.com brought the bug to light.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-08T18:08:05.210Z
Answers.LastActivityDate: 2016-04-08T18:08:05.210Z
Answers.UserDisplayName: Chris
Answers.Body: <p>It probably means that paypal doesn't ping back properly your civi to let it know if it processed properly the card. Unfortunately, they are a lot of reasons to get that call not working, either because paypal try to IPN elsewhere, with a different format than expected or that something is wrong on how we process it (given it broke after an upgrade, the most likely option)</p>
  
  <p>Can you check on the log if you have any error that might clarify what is the issue?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-19T23:11:52.273Z
Answers.Text: I have checked the wp error log. There are 10 items on the log, some of them spanning back to October of last year, none of them involving CiviCRM.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-19T23:19:26.607Z
Answers.Text: Paypal recognizes the payments as processed. CiviCRM is not sending out Confirmation emails. Also, the upgrade to 4.7.2 does not seem to have fixed the error. Thank you so much for your help.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-22T21:58:54.353Z
Answers.Text: Additional information - the person who administers civicrm now suggests she may have made some changes to an event about the same time, but the change was only for a specific event, and only to create a personal campaign page. She has since removed the personal campaign page, and we're still seeing the same results. Also, it's not just campaigns but memberships and member renewals that are affected with "Pending, incomplete transaction", so the problem is likely something not necessarily related to this specific event.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-23T17:35:58.573Z
Answers.Text: I have the same issue with CiviCRM 4.7.2 on the latest WordPress stable. Paypal IPN http requests are received and entries created in civicrm_system_log, but the error logs show "Could not find payment processor for contribution record: N". I suspect that http://civicrm.stackexchange.com/questions/9753/paypal-recurring-transactions-are-broken-in-4-7 is related.
Answers.UserDisplayName: Christian Wach
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-24T12:39:38.387Z
Answers.Text: What kind of WordPress install do you have? I have just fixed one part of the problem in multisite and multi-network situations: https://issues.civicrm.org/jira/browse/CRM-18099
Answers.UserDisplayName: Christian Wach
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-27T14:08:43.437Z
Answers.Text: Mine is a single-site install. Like Logan Bear, I have several inactive payment processors that only kick in when the date is right. I'm not sure the jira link applies in this case.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-18T09:07:15.757Z
Answers.LastActivityDate: 2016-02-18T09:07:15.757Z
Answers.UserDisplayName: Xavier
Answers.Body: <p>I've found a fix that works for me, but I cannot guarantee that it won't have consequences for other transactions. A fully audited fix for this needs the involvement of people who know the code a lot better than me. Having said that, you can try the following:</p>
  
  <p>Change this:</p>
  
  <pre><code>throw new CRM_Core_Exception
  </code></pre>
  
  <p>to this:</p>
  
  <pre><code>CRM_Core_Error::debug_log_message
  </code></pre>
  
  <p>in this file on line 177 for WordPress:</p>
  
  <blockquote>
    <p>/wp-content/plugins/civicrm/civicrm/CRM/Core/Payment/BaseIPN.php</p>
  </blockquote>
  
  <p>or this file on line 178 for Joomla: </p>
  
  <blockquote>
    <p>/administrator/components/com_civicrm/civicrm/CRM/Core/Payment/BaseIPN.php</p>
  </blockquote>
  
  <p>There's a ticket on Jira that seems to be relevant here: <a href="https://issues.civicrm.org/jira/browse/CRM-18107" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-18107</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-27T15:13:07.437Z
Answers.Text: This would only be a temporary fix though, right? Because we're just hiding the action on this error in the log -- and any other future-introduced flaw in this part of the code? Surely this is not a permanent fix.
Answers.UserDisplayName: Chris
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-28T22:01:27.690Z
Answers.Text: Indeed. As I said, "a fully audited fix for this needs the involvement of people who know the code a lot better than me" :-)
Answers.UserDisplayName: Christian Wach
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-05T21:26:56.260Z
Answers.Text: Subscribing. This resolved a nearly identical issue with one of my Joomla installs. I'll be watching for a bugfix or more info.
Answers.UserDisplayName: isherwood
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-25T12:11:07.947Z
Answers.LastActivityDate: 2016-03-06T16:09:42.297Z
Answers.LastEditDate: 2016-03-06T16:09:42.297Z
Answers.UserDisplayName: Christian Wach
Body: <p>Wordpress 4.4.2
  CiviCRM Just upgraded from 4.6.10 to 4.7.1 last week.</p>
  
  <p>Ever since we've upgraded, CiviCRM allows payments to be made via PayPal, but event registrations and membership renewals are now always marked as "Pending (incomplete transaction)". We have to manually go to PayPal, check whether they've actually paid, confirm and then edit the pending flag manually so that the transaction shows as complete in CiviCRM. </p>
  
  <p>Additionally, email confirmations from CiviCRM are not going out.</p>
  
  <p>This is causing much more work than we had to do last week before we updated to CiviCRM 4.7.1</p>
  
  <p>Test event registrations and renewals work as expected. Live ones don't.</p>
  
  <p>On the off chance that 4.7.2 has a fix, I've just upgraded successfully to the latest version. Until I see some renewals or event registrations, I won't know if that's fixed it.</p>
  
  <p>I'd be grateful if someone can tell me if 4.7.2 had the fix or if this is something outside the scope of 4.7.2. </p>
  
  <p>(see image below)</p>
  
  <p>Cheers,</p>
  
  <p>Chris</p>
  
  <p><a href="https://i.sstatic.net/x5Tl8.png" rel="noreferrer"><img src="https://i.sstatic.net/x5Tl8.png" alt="pending-incomplete transation"></a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-06T16:39:39.800Z
Comments.Text: There isn't enough full coverage regression testing. We should have stuck with the version from about a year ago.. the features we needed seemed to work then.
Comments.UserDisplayName: P a u l
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-07T02:27:34.707Z
Comments.Text: I wish I knew enough about the code to make a reasonable contribution.
Comments.UserDisplayName: Chris
Tags: <upgrade><paypal><4.7><pending>
Title: Paypal Interruptus - Wordpress w/ CiviCRM 4.7.1
ThreadText: # Paypal Interruptus - Wordpress w/ CiviCRM 4.7.1
  
  (Asked by: username_0 on 2016-02-18)
  
  Wordpress 4.4.2
  CiviCRM Just upgraded from 4.6.10 to 4.7.1 last week.
  
  Ever since we've upgraded, CiviCRM allows payments to be made via PayPal, but event registrations and membership renewals are now always marked as "Pending (incomplete transaction)". We have to manually go to PayPal, check whether they've actually paid, confirm and then edit the pending flag manually so that the transaction shows as complete in CiviCRM.
  
  Additionally, email confirmations from CiviCRM are not going out.
  
  This is causing much more work than we had to do last week before we updated to CiviCRM 4.7.1
  
  Test event registrations and renewals work as expected. Live ones don't.
  
  On the off chance that 4.7.2 has a fix, I've just upgraded successfully to the latest version. Until I see some renewals or event registrations, I won't know if that's fixed it.
  
  I'd be grateful if someone can tell me if 4.7.2 had the fix or if this is something outside the scope of 4.7.2.
  
  (see image below)
  
  Cheers,
  
  username_0
  
  [![pending-incomplete transation](https://i.sstatic.net/x5Tl8.png)](https://i.sstatic.net/x5Tl8.png)
  
  **Tags:** upgrade, paypal, 4.7, pending
  
  > **Comments:**
  > **username_1**: There isn't enough full coverage regression testing. We should have stuck with the version from about a year ago.. the features we needed seemed to work then.  
  > **username_0**: I wish I knew enough about the code to make a reasonable contribution.  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_0 on 2016-04-08. Score: 1 | Accepted answer
  
  The answer now is to upgrade from 4.7.1 to 4.7.4 or better.
  Apparently a number of paypal processes were corrected after this and other posts on civicrm.stackexchange.com brought the bug to light.
  
  
  ---
  
  ### Answer by username_2 on 2016-02-18. Score: 2
  
  It probably means that paypal doesn't ping back properly your civi to let it know if it processed properly the card. Unfortunately, they are a lot of reasons to get that call not working, either because paypal try to IPN elsewhere, with a different format than expected or that something is wrong on how we process it (given it broke after an upgrade, the most likely option)
  
  Can you check on the log if you have any error that might clarify what is the issue?
  
  > **Comments:**
  > **username_0**: I have checked the wp error log. There are 10 items on the log, some of them spanning back to October of last year, none of them involving CiviCRM.  
  > **username_0**: Paypal recognizes the payments as processed. CiviCRM is not sending out Confirmation emails. Also, the upgrade to 4.7.2 does not seem to have fixed the error. Thank you so much for your help.  
  > **username_0**: Additional information - the person who administers civicrm now suggests she may have made some changes to an event about the same time, but the change was only for a specific event, and only to create a personal campaign page. She has since removed the personal campaign page, and we're still seeing the same results. Also, it's not just campaigns but memberships and member renewals that are affected with "Pending, incomplete transaction", so the problem is likely something not necessarily related to this specific event.  
  > **username_3**: I have the same issue with CiviCRM 4.7.2 on the latest WordPress stable. Paypal IPN http requests are received and entries created in civicrm_system_log, but the error logs show "Could not find payment processor for contribution record: N". I suspect that http://civicrm.stackexchange.com/questions/9753/paypal-recurring-transactions-are-broken-in-4-7 is related.  
  > **username_3**: What kind of WordPress install do you have? I have just fixed one part of the problem in multisite and multi-network situations: https://issues.civicrm.org/jira/browse/CRM-18099  
  > **username_0**: Mine is a single-site install. Like Logan Bear, I have several inactive payment processors that only kick in when the date is right. I'm not sure the jira link applies in this case.  
  
  ---
  
  ### Answer by username_3 on 2016-02-25. Score: 2
  
  I've found a fix that works for me, but I cannot guarantee that it won't have consequences for other transactions. A fully audited fix for this needs the involvement of people who know the code a lot better than me. Having said that, you can try the following:
  Change this:
  throw new CRM_Core_Exception
  
  to this:
  CRM_Core_Error::debug_log_message
  
  in this file on line 177 for WordPress:
  
  /wp-content/plugins/civicrm/civicrm/CRM/Core/Payment/BaseIPN.php
  
  or this file on line 178 for Joomla: 
  
  /administrator/components/com_civicrm/civicrm/CRM/Core/Payment/BaseIPN.php
  
  There's a ticket on Jira that seems to be relevant here: https://issues.civicrm.org/jira/browse/CRM-18107
  
  > **Comments:**
  > **username_0**: This would only be a temporary fix though, right? Because we're just hiding the action on this error in the log -- and any other future-introduced flaw in this part of the code? Surely this is not a permanent fix.  
  > **username_3**: Indeed. As I said, "a fully audited fix for this needs the involvement of people who know the code a lot better than me" :-)  
  > **username_4**: Subscribing. This resolved a nearly identical issue with one of my Joomla installs. I'll be watching for a bugfix or more info.  
  
  ---
  
  