CiviCRM Community Forums (archive)

My CiviContribute signup/registration form works fine, but the user is returned to the signup form rather than seeing the thanks content configured in CiviContribute. On the return page, I believe they should see the content from the "Thanks / Receipt" page. The email seems to be generated OK.

I've only tested this with Paypal Standard (both test and live mode, by configuring both to use Paypal Sandbox).

I have duplicated this issue on the CiviCRM demo server.

Live Page: http://demo.civicrm.org/drupal/civicrm/contribute/transact?reset=1&id=23

Returned page: http://demo.civicrm.org/drupal/civicrm/contribute/transact?txn_type=web_accept&payment_date=19%3A37%3A31+Sep+09%2C+2007+PDT&last_name=User&residence_country=US&pending_reason=unilateral&item_name=Online+Contribution%3A+Test+Membership+HOU&payment_gross=0.01&mc_currency=USD&payment_type=instant&payer_status=verified&verify_sign=AAWqx.JYxopp4PA4G.qqI1-B5zerAbgBteFFd9.QhJJZWE7Bq7pYde.1&test_ipn=1&payer_email=test_1189135281_per%40greens.org.nz&tax=0.00&txn_id=0&first_name=Test&receiver_email=sing%40tcwc.org&quantity=1&payer_id=FQ4AC5CWHHTS2&invoice=ef7d90de4842c97d05d91c4c3803976c&item_number=&payment_status=Pending&shipping=0.00&mc_gross=0.01&custom=&charset=windows-1252&notify_version=2.4&merchant_return_link=Return+to+Merchant

Could this be a configuration issue? Does it affect other processors apart from Paypal Standard?

Here is the code that checks for this "exception" condition from paypal"

        if ( isset( $_GET['payment_date'] )                                       &&
             isset( $_GET['merchant_return_link'] )                               &&
             CRM_Utils_Array::value( 'payment_status', $_GET ) == 'Completed'     &&
             $paymentProcessor['payment_processor_type'] == "PayPal_Standard" ) {
            return true;
        }

In your case payment_status is Pending, hence we do not do a redirect. You could augment the logic to make it Completed or Pending. PayPal does not work as advertised in the documentation and hence the gross workaround above

lobo