philiprabbett

I think PayPal is part of the problem because when you Google PayPal Credit, the American website says it’s only for US customers but going to the UK site says UK supports it also (obviously) so my assumption is that’s part of the problem.

They’ve changed the code slightly since I originally had this issue. I’ve raised a bug report with WooCommerce since we are getting nowhere here… It’s possible to just change that to return true but I’m not sure of any fallout since it’s been a while from when I first patched this. The problem with patching is that we can’t update the plugin after since it would undo the patch and therefore any potential security fixes would be missed leaving your store vulnerable to attack.

This is wrong, totally wrong. Essentially we cannot use this plugin for PayPal credit in the UK. As I’ve stated before, the plugin only allows PayPal credit for stores that are in the US and WooCommerce currency is set to US Dollars.

Stating that this is an issue with PayPal is nonsense. We have PayPal credit enabled on our accounts but cannot use this plugin for accepting PayPal credit as we are not in the US and operating with US Dollars. The developers of this plugin need to update the plugin to better handle this. The responsibility lays with the plugin developers NOT PayPal!

function wc_gateway_ppec_is_credit_supported() {
	$base = wc_get_base_location();
	return 'US' === $base['country'] && 'USD' === get_woocommerce_currency();
}

The only part of this plugin that appears in the cart page is the ‘- or -‘ text, the original HTML markup is viewable but the script is missing, by changing the wp_enqueue_script to contain the details of the wp_register_script I’m able to get this working and presently using a fork of the plugin.

My theme is a custom built theme using Timber but the hooking methods are all the same. I’ll have a dig about using storefront theme, I assume that would WooCommerce’s Twenty Nineteen equivalent?

FYI: Restarting PHP kicks the site back into action again

Hi @treibalen,

The plugin has a check for whether PayPal credit is supported by matching the websites currency and the store base location, it does not check with PayPal if the account supports PayPal Credit

function wc_gateway_ppec_is_credit_supported() {
	$base = wc_get_base_location();
	return 'US' === $base['country'] && 'USD' === get_woocommerce_currency();
}

Note for plugin author, the problem here is that the plugin does not yet handle the GDPR fields. This GDPR field was recently introduced to the API that this plugin uses.

See this blog post for further information: https://medium.com/@hagenverfolgt/how-to-use-mailchimp-rest-api-with-php-the-right-way-in-2018-96e368ecc976

Yes, curious as to why you didn’t opt for registering custom post type and using WordPress post edit screen but rather went a custom route instead.

When will the report-uri be configurable?

I would also like to see RFG plugin utilise the Site Icon API.

I’ve found a hacky way around this using the do_shortcode_tag filter.

You’ll find the variable is mislabelled within the tag version but not within the trunk version and WordPress is pulling from the tag version, I downgraded the version and upgraded within WP Admin and the same issue occurred.

Check it out:
https://plugins.trac.www.ads-software.com/browser/contact-form-7-lead-info-with-country/tags/1.4.0/wpshore_cf7_lead_tracking.php#L64

https://plugins.trac.www.ads-software.com/browser/contact-form-7-lead-info-with-country/trunk/wpshore_cf7_lead_tracking.php#L64

Within /cf7-multi-step/contact-form-7-multi-step.php

At line 132, change

if (WPCF7_VERIFY_NONCE && ! wpcf7_verify_nonce($_POST['_wpnonce'], $contact_form->id())) {

to

if (WPCF7_VERIFY_NONCE && ! wpcf7_verify_nonce($_POST['_wpcf7_nonce'], $contact_form->id())) {

Contact Form 7 changed from _wpnonce to _wpcf7_nonce AFAIK, this fixed it for me.

It’s possible but not in this version. I’ve been meaning to update the plugin with more options. Hopefully soon.

It is perfectly fine to have all those options enabled. It just means that the JavaScript files will possibly be loaded unnecessarily on certain sections on the frontend if the functionality isn’t required on those pages, for example, home page, etc.