Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 SSL Cert issue: Patch for CA CERT not found | Event Espresso - Staging Server
I’ve contacted my hosting company (Hostek) and they’ve given me this workaround, which I am trying to integrate with your line of code after line 91 in the Paypal.php file:
<pre class=”brush: php; gutter: true; first-line: 1; highlight: []; html-script: false”>$error["set_timeout"] = curl_setopt($ch, CURLOPT_TIMEOUT, 45); // Sets a time limit for curl in seconds (do not set too low)
$error["set_post"] = curl_setopt($ch, CURLOPT_POST, 1); // Set curl to send data using post
$error["set_post_fields"] = curl_setopt($ch, CURLOPT_POSTFIELDS, $req); // Add the request parameters to the post
curl_setopt($ch, CURLOPT_CAINFO, dirname("/PHP") . 'ca-bundle.crt '); // Patch for CA CERT not found
$errors .= $error["set_host"] ? "Success" : "Failure";
Here is what my hosting company told me to use as a workaround
Mike,
It looks like in order to fix the error you were getting, one of the following two things must be done in the CURL configuration used by the PayPal script:
Our techs used the second option (by adding it to the PayPal.php) so that your script could verify the PayPal cert is trusted. The other option was to disable it completely, which is obviously a last resort.
This topic was modified 11 years, 5 months ago by Michael Bernhard.
This topic was modified 11 years, 5 months ago by Michael Bernhard.
The support post ‘SSL Cert issue: Patch for CA CERT not found’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.