Hot answers tagged

8

It seems it is about your ssl connection, so it's on the openssl layer connected to your webserver (apache or nginx). Test your ssl connection with that site, https://www.ssllabs.com/ssltest/ it will tell you what needs to be improved. In short, nothing to do with civicrm, but upgrading to the latest version is always a good idea anyway


7

No, PayPal state that SSL will not required for IPN. I contacted PayPal MTS to confirm and got the responses below: PayPal seem to be saying if you have SSL yourself, your certificate and its chain need SHA-256 not SHA-1 both for PayPal and modern browser support, when you connect to their server, your webserver must accommodate their SHA-256 certificate. ...


5

This is a notice regarding BOTH your website's SSL, and the ability of CiviCRM to use your system PHP and SSL libraries to connect to Paypal's SSL. SHA-256 support on your site If you use SSL on your website, you need to check that your certificate is SHA-256. This can be done quickly using shaaaaaaaaaaaaa.com, and you can get a more thorough review from ...


4

The way it works with paypal standard is that paypal informs civicrm that the payment has been done in the background via IPN (instant payment notification) It means that paypal is sending information to a specific page on civicrm with the proper data (eg this payment has been successful) then your server sends these information back to a specific page on ...


4

Could you create a new contact with just a first and last name (no address, phone, or anything else that might go in a separate table somewhere) and then change that new contact's ID in the database to 1212? Then you could merge again, making sure to keep the new contact and transfer all of the other information over during the merge. (Try on a copy of the ...


4

Issue had been filed https://issues.civicrm.org/jira/browse/CRM-18483 and this is my fix https://github.com/civicrm/civicrm-core/pull/8270/files As earlier in case of drupal site, CRM_Utils_System::loadBootStrap() eventually calls CRM_Utils_System_Drupal::loadBootStrap() and fails at https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/System/...


4

The issues related to paypal standard and webform_civicrm have already been resolved. I've just updated the wiki documentation to reflect this.


4

Ken West, I guess your cron job 'Clean-up Temporary Data and Files' must be running when your site is busy. The session key is not an usual error. CiviCRM stores sessions variables into its database int the form of cache. When 'Clean-up Temporary Data and Files' schedule job is executed or CiviCRM cache is cleared manually the cache table is truncated. So ...


4

From my experience, PayPal Express and PayPal Payments Pro have always conflicted with Civi. PayPal Standard works fine for both recurring and one-time payments, but the other two options do not work for recurring payments. My organization went back and forth with PayPal over this issue for months. Then we tried to fix it on our end with zero positive ...


3

I had recently looked into this for our website, so I think I can answer this question. First, it is important to understand what this is. It is not accepting PayPal through Authorize.net, which is what it sounds like. What happens is you setup a PayPal account for your organization, and then you link it to your Authorize.net account. That linking though ...


3

You may have found a bug in the webform_civicrm module. I don't have a great way of testing paypal right now, but I've just made a few tweaks which I think will help - can you try it out? Download the patched version here: https://github.com/colemanw/webform_civicrm/archive/ipn.zip


3

Glad you found an answer. An alternative solution would be to log into PayPal - you can change the parameters of a recurring payment IPN manually in Paypal. Note that last I checked, they use some Javascript to limit the length of the field where you can change the URL, and they limit it to less than the full permitted length. When I change the URL ...


3

What I discovered with the help of a friend who has lots of experience in CIviCRM is that I had set up the payment processor with the default URL for both LIve and TEst but used the SAndbox credentials only. By putting in the sandbox urls as the live urls. it fixed the problem.


3

I found the problem. I had "BIlling address required" turned on and that forced CiviEvent to demand more info and not let the user go to Paypal. I turned that off and it works.


3

My understanding is that part of your agreement with PayPal is to offer the option to pay with PayPal. While you could use jQuery to hide the button or alter CiviCRM's code to remove it from display, you've promised PayPal that you won't. There are stories (urban legends or actual instances, I'm not sure) of PayPal going after folks who hide the Pay with ...


3

I used the alterPaymentProcessorParams Hook to override the parameters 'return' and 'cancel_return'. The code looks like this: function civicrm_alterPaymentProcessorParams($paymentObj, &$rawParams, &$cookedParams) { if ($paymentObj->_processorName == "PayPal Standard") { if (!empty($rawParams['successUrl'])) { ...


3

You're experiencing the bug documented at CRM-21595. You will need to apply the patch or wait for CiviCRM 4.7.30. Most people won't experience this bug if they disable "Pay Later" as an option.


3

Apparently Paypal charges extra for recurring functionality and you have not subscribed to the additional $30/mo DPRP service. DPRP is disabled. DPRP is disabled for this merchant. https://www.paypal-community.com/t5/About-Business-Archive/quot-DPRP-is-disabled-for-this-merchant-quot-plz-help/m-p/991717#M14689 In your bounty comment you state: I am ...


3

@andygoodall thanks for posting this, we believe we have a fix for your issue, We are looking to conduct a point release for 5.10 to fix the issue however i would recommend if possible manually applying the change described in this PR


3

You would need to reach out to Paypal and Stripe directly to ask them about how to initiate the process of transferring your recurring giving. I would suggest inventorying your existing recurring records in Paypal first, to see how complex the data is; in a recent transition to Stripe, we encountered some challenges with constituents who had multiple ...


3

Having reviewed this I believe that your Paypal is possibly configured to point to an older version of the IPN path. You can change this yourself within your Paypal account, the docs I can see suggest: To configure Instant Payments Notification (IPN) for your PayPal account Click: Profile, under Selling preferences click "Instant Payment Notification ...


2

The bug was fixed by Yashodha of the core team in 4.6.9: https://issues.civicrm.org/jira/browse/CRM-17015 In the mean time, there is a 3 line patch that you can apply: https://github.com/civicrm/civicrm-core/pull/6720/files


2

The error is because the max participant limit is reached for the price option. You probably need to check the Max Participant limit in your Price set/field


2

Did you check your resource url setting? If so, what is it? It needs to be a complete url, as explained in the help for that field: http://mysite.mydomain.com/sites/all/modules/civicrm/


2

I received the same message (I'm using PayPal Standard with CiviCRM on Drupal). I don't believe we need to do anything about it, because CiviCRM doesn't interact with PayPal's dispute process. My experience has always been that if a payment is reversed in PayPal, the reversal is not automatically reflected in CiviCRM -- instead, I have to manually edit the ...


2

templates/CRM/Core/BillingBlock.tpl Note that the template is quite programmatic and gets in pretty much all of its info via template variables. I suspect you will benefit from reading the developer documentation which will help you with the Civi learning curve.


2

I have been directed to this patch: https://www.drupal.org/node/2177647 I can't tell you whether it works or not yet since it will take a few weeks to be sure. But it seems to be the going solution.


2

This patch fixes the problem for me: https://github.com/civicrm/civicrm-core/pull/6900


2

Update your site to CiviCRM 4.6.7 This was a bug, reported at https://issues.civicrm.org/jira/browse/CRM-14536 We had this problem on our site, and it was fixed as of 4.6.7. Update your site to the latest version, and you should be all set!


2

You may want to follow progress on this issue which seems related: https://issues.civicrm.org/jira/browse/CRM-17082


Only top voted, non community-wiki answers of a minimum length are eligible