Answers.Body: <p>The answer is that I'm not sure why this is no longer working for you. </p>
  
  <ul>
  <li>All our 4.6 sites have been upgraded to 4.6.26 and are using iATS
  1.5.3 and I've had no reports of anything breaking. </li>
  <li>I've just confirmed myself by making a donation to one of our projects that I
  get to the Thank you page.</li>
  </ul>
  
  <p>There is a bit of Javascript on that Make Contribution button. Ask your developer/support to open up a Firebug/Console to start the hunt as to what may be going on with your Contribution page.</p>
  
  <p>From your Comments I see DOMPDF is throwing an error -> it is known to blow up at times - best to disable PDF creation for your receipt. It's one of those obscure settings under Misc -> civicrm/admin/setting/misc?reset=1 -> hit No on Attach PDF copy to receipts. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T17:54:58.213Z
Answers.Text: Thanks Karin. I believe we updated from 4.6.19? Not sure. I'll try to check that by looking at the archives. In any case, it appears to be a timeout issue: Fatal error: Allowed memory size of 367001600 bytes exhausted (tried to allocate 130968 bytes) in /home/lifechallengesem/public_html/data/sites/all/modules/civicrm/vendor/dompdf/dompdf/src/Css/Style.php on line 774
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T17:56:27.450Z
Answers.Text: BTW: the recurring payments are not updating the next scheduled payment field in the tables either. So recurring payments are not completing in a way that prevents them from being triggered again. I have to go into the table to update the next scheduled.
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T17:58:28.863Z
Answers.Text: Pretty sure it has nothing to do with the button. Memory allocation problem? Even so, don't know why a transaction would now exceed any memory limits, since nothing has changed regarding memory limits.
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T18:09:15.820Z
Answers.Text: One more note: In troubleshooting, I did disable and then re-enable 1.5.3 just to be sure everything was re-engaged after update to 4.6.26. Still no luck. Transaction times out but shows up in iATS Payments Admin and User Record (and obviously, in the iATS server).
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T18:10:23.567Z
Answers.Text: Hmmm...what could cause that last step in the process to time out like that?
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T18:12:05.687Z
Answers.Text: Re: recurring: I just double checked and a recurring with 4.6.26 and 1.53 from early this AM -> had its next scheduled date properly advanced to March 14 - 2017, so not sure what's going on with that. Of course if you have set things up such that you're trying to send out receipts for every single recurring contribution and it was trying to attached DOMPDF receipts - then... perhaps it got stuck on that.
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T18:12:47.103Z
Answers.Text: I've updated my answer -> see above;
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T19:05:53.557Z
Answers.Text: Thanks. Made the change. Didn't work. I turned "Attach PDF" off and still timed out. I am going to contact the server administrator for any apache logs that might be relevant.
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T19:24:33.840Z
Answers.Text: BTW: This is happening on ALL transactions, not just event registrations (The PDF creation configuration seems to only apply to event registrations).
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T19:51:14.077Z
Answers.Text: Actually it does apply to online contributions as well - as the field/help explains: "Attach PDF copy to receipts Yes No - If enabled, CiviCRM sends PDF receipt as an attachment during event signup or online contribution."
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T20:18:12.800Z
Answers.Text: Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/53640/discussion-between-john-richardson-and-karing-semper-it).
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-14T16:59:18.923Z
Answers.LastActivityDate: 2017-02-14T18:08:22.797Z
Answers.LastEditDate: 2017-02-14T18:08:22.797Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>Just updated to CiviCRM 4.6.26 from 4.6.x. Using iATS 1.5.3. Using D7. The user does not experience a completed transaction even though the transaction is complete through iATS and shows complete on user record (and in iATS dashboard in civi). The submit or "make contribution" link appears to hang up. No confirmation is sent to user or administrator. This results in the user attempting to resubmit. Any solutions? Any troubleshooting tips?</p>
  
  <p>BTW: we have changed no configurations on contribution/registration pages. Previously working. But now they all hang up, we get no confirmation or "success" notification on any of our pages.</p>
  
  <p>This has been resolved here: <a href="https://civicrm.stackexchange.com/questions/17343/iats-scheduled-job-for-recurring-payments-does-not-finish-in-the-logs-how-can/17387#17387">iATS Scheduled job for recurring payments does not &quot;finish&quot; in the logs. How can I fix this or troubleshoot further?</a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-14T05:08:26.437Z
Comments.Text: Just to be clear: you suspect this is caused by the upgrade to 4.6.26? From what 4.6.x did you upgrade from?
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-23T17:48:10.957Z
Comments.Text: This problem has been resolved here: http://civicrm.stackexchange.com/questions/17343/iats-scheduled-job-for-recurring-payments-does-not-finish-in-the-logs-how-can/17387#17387
Comments.UserDisplayName: John Richardson
Tags: <civicontribute><iats>
Title: Why does the user not get a "transaction complete" or "success" confirmation message after submitting an online transaction?
ThreadText: # Why does the user not get a "transaction complete" or "success" confirmation message after submitting an online transaction?
  
  (Asked by: username_0 on 2017-02-14)
  
  Just updated to CiviCRM 4.6.26 from 4.6.x. Using iATS 1.5.3. Using D7. The user does not experience a completed transaction even though the transaction is complete through iATS and shows complete on user record (and in iATS dashboard in civi). The submit or "make contribution" link appears to hang up. No confirmation is sent to user or administrator. This results in the user attempting to resubmit. Any solutions? Any troubleshooting tips?
  
  BTW: we have changed no configurations on contribution/registration pages. Previously working. But now they all hang up, we get no confirmation or "success" notification on any of our pages.
  
  This has been resolved here: [iATS Scheduled job for recurring payments does not "finish" in the logs. How can I fix this or troubleshoot further?](https://civicrm.stackexchange.com/questions/17343/iats-scheduled-job-for-recurring-payments-does-not-finish-in-the-logs-how-can/17387#17387)
  
  **Tags:** civicontribute, iats
  
  > **Comments:**
  > **username_1**: Just to be clear: you suspect this is caused by the upgrade to 4.6.26? From what 4.6.x did you upgrade from?  
  > **username_0**: This problem has been resolved here: http://civicrm.stackexchange.com/questions/17343/iats-scheduled-job-for-recurring-payments-does-not-finish-in-the-logs-how-can/17387#17387  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-02-14. Score: 1
  
  The answer is that I'm not sure why this is no longer working for you.
  
  * All our 4.6 sites have been upgraded to 4.6.26 and are using iATS
    1.5.3 and I've had no reports of anything breaking.
  * I've just confirmed myself by making a donation to one of our projects that I
    get to the Thank you page.
  
  There is a bit of Javascript on that Make Contribution button. Ask your developer/support to open up a Firebug/Console to start the hunt as to what may be going on with your Contribution page.
  
  From your Comments I see DOMPDF is throwing an error -> it is known to blow up at times - best to disable PDF creation for your receipt. It's one of those obscure settings under Misc -> civicrm/admin/setting/misc?reset=1 -> hit No on Attach PDF copy to receipts.
  
  > **Comments:**
  > **username_0**: Thanks Karin. I believe we updated from 4.6.19? Not sure. I'll try to check that by looking at the archives. In any case, it appears to be a timeout issue: Fatal error: Allowed memory size of 367001600 bytes exhausted (tried to allocate 130968 bytes) in /home/lifechallengesem/public_html/data/sites/all/modules/civicrm/vendor/dompdf/dompdf/src/Css/Style.php on line 774  
  > **username_0**: BTW: the recurring payments are not updating the next scheduled payment field in the tables either. So recurring payments are not completing in a way that prevents them from being triggered again. I have to go into the table to update the next scheduled.  
  > **username_0**: Pretty sure it has nothing to do with the button. Memory allocation problem? Even so, don't know why a transaction would now exceed any memory limits, since nothing has changed regarding memory limits.  
  > **username_0**: One more note: In troubleshooting, I did disable and then re-enable 1.5.3 just to be sure everything was re-engaged after update to 4.6.26. Still no luck. Transaction times out but shows up in iATS Payments Admin and User Record (and obviously, in the iATS server).  
  > **username_0**: Hmmm...what could cause that last step in the process to time out like that?  
  > **username_1**: Re: recurring: I just double checked and a recurring with 4.6.26 and 1.53 from early this AM -> had its next scheduled date properly advanced to March 14 - 2017, so not sure what's going on with that. Of course if you have set things up such that you're trying to send out receipts for every single recurring contribution and it was trying to attached DOMPDF receipts - then... perhaps it got stuck on that.  
  > **username_1**: I've updated my answer -> see above;  
  > **username_0**: Thanks. Made the change. Didn't work. I turned "Attach PDF" off and still timed out. I am going to contact the server administrator for any apache logs that might be relevant.  
  > **username_0**: BTW: This is happening on ALL transactions, not just event registrations (The PDF creation configuration seems to only apply to event registrations).  
  > **username_1**: Actually it does apply to online contributions as well - as the field/help explains: "Attach PDF copy to receipts Yes No - If enabled, CiviCRM sends PDF receipt as an attachment during event signup or online contribution."  
  > **username_0**: Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/53640/discussion-between-john-richardson-and-karing-semper-it).  
  
  ---
  
  