stepfaul

Hi, thanks for taking a look.

My sites WordPress and WooCommerce are the latest versions. I am able to reproduce this issue from 4 different PC’s and have even been able to reproduce it on some of the other site url’s posted in this support forum.

Essentially if you have any saved details in Edge such as first name, surname, address etc and at checkout if you try to edit the auto completed details by inserting a space either before, in the middle or after the text it does not work. in addition to this if you select the ‘undo autofill’ option to remove any auto completed information, spaces still do not work even when dealing with a blank field.

This issue has already lost me a sale as the customer could not edit the auto completed information saved in Edge and I am sure it wont be the last. I appreciate this may be a browser related issue but this will be impacting other WooCommerce sites.

*** As an update I have just browsed to a Shopify sites checkout as a comparison and cannot reproduce the issue ***

• This reply was modified 3 weeks, 5 days ago by stepfaul.

+1 this needs much greater visibility. I should not have to search around for the log before upgrading. Thanks

@niklasinpsyde Apologies for the delay in responding as I have been away for a couple of days. I have just tested a full end to end transaction on my staging site using Amazon Pay and all worked as expected.

Thanks very much for looking into this!

Kind regards

Steve.

`Hello @stepfaul

we have been trying to get our Amazon account to work in order to test this issue, but this seems to take a bit longer than expected. In order to check this issue now, I want to ask you if it would be possible to use your staging site for this purpose.

If this is an option, please open a support ticket with us as described here, so we can get the access details securely: https://paypal.inpsyde.com/docs/how-to-request-support-via-widget-on-the-website/

Kind regards,
Joost`

Hi @joostvandevijver

I have opened a support ticket ref PPC-155 as requested.

Kind regards

Steve.

Thanks @joostvandevijver

I have since managed to configure Amazon Pay on my staging site – https:// staging.littletigergifts co uk/ and can confirm that the issue still occurs. If I disable the option under WooCommerce > Settings > Payments the issue still occurs. The only way to resolve things is to disable the PayPal Payments Plugin from within plugins.

I have left the staging site with plugin enabled so you can have a test. The site is running the latest version of WooCommerce (5.5.1) but I have not upgraded to WP 5.8 yet so it is running 5.7.2 All plugins are the latest versions.

To reproduce the issue, select the Amazon Pay button from either the cart or checkout, login to Amazon Pay, confirm payment details and select the button to continue with payment – this will then attempt to take you back to my site where upon return the fatal error page is displayed.

Hope this helps.

Steve.

@peachpay – Thanks for getting this resolved so quickly. Things look good now!

Sorry, don’t quite know what happened there but just tried again after clearing all caches and still the same error. Almost seems to be flapping between working and not working…

Bizarely this is now working after waiting 15-20 minutes and not doing anything else!

I will check again in the morning and after clearing caches again and let you know.

Thanks for creating the issue @niklasinpsyde I have disabled the option to show on the cart page for the time being.

Kind regards

Steve.

Just to add that although I don’t normally like bugs the following

However, changing the button layout from vertical to horizontal can lead to only the PayPal button being shown in some environments.

Works for me and only shows the PayPal button and not the Sofort or Debit or Credit Card buttons which is perfect for me.

I appreciate this is subject to change so will keep an eye on things but for now the workaround is perfect.

Thanks again

Steve.

Thanks for the mega quick response! I will try your workaround and also contact PayPal.

Many thanks

Steve.

Hi @stepfaul!

You might use a small code snippet like so:

https://stackoverflow.com/questions/37568595/how-to-remove-specific-country-in-woocommerce

Where the country would be GG and you can extend the array to add more countries.

Alternatively, you could use a plugin like https://woocommerce.com/products/shipping-locations-pro/

Cheers!

Apologies @rynald0s for being rude and not responding sooner. The stackoverflow code below worked just great!

function woo_remove_specific_country( $country ) 
{
   unset($country["GG"]);
   return $country; 
}
add_filter( 'woocommerce_countries', 'woo_remove_specific_country', 10, 1 );

I did not search for a functions.php based solution as I believed that WooCommerce has got the country classification wrong but either way this is a quick solution to my problem.

Thanks

Steve.

Hi Stuart,

Thanks for the quick response, I just added js/jquery/jquery.min.js to the list of scripts to exclude in the Autoptimize plugin and all is now good. Previously I just had js/jquery/jquery.js.

Kind regards

Steve.

Thanks for the very quick response, I added js/jquery/jquery.min.js to the list of scripts to exclude and all is now good. Previously I just had js/jquery/jquery.js.

• This reply was modified 3 years, 9 months ago by stepfaul.

Thanks Tom,

Just one more question (apologies as I have only just had a chance to test this fully), I have added the snippet to my functions.php but when running a Google page speed test and looking at the Desktop results I can see the font files for the Google font sourcesanpro are triggering an opportunity. I think this is because the font does not have font-display: swap in the css like the Google Example:

@font-face {
  font-family: 'Pacifico';
  font-style: normal;
  font-weight: 400;
  src: local('Pacifico Regular'), local('Pacifico-Regular'), url(https://fonts.gstatic.com/s/pacifico/v12/FwZY7-Qmy14u9lezJ-6H6MmBp0u-.woff2) format('woff2');
  font-display: swap;
}

Might it be possible to add this to all the font variations? This would at least improve things from that perspective.

I hope I am not being picky but I am trying to prepare the site as best as I can for the up and coming changes where Google will use core web vitals as a ranking factor.

Thanks again.

Steve.