jh

@premkumarbset I’ve got a solution – I don’t want to publish it here incase these fraudsters see it.

Feel free to reach out ot my github

https://github.com/JethroHazelhurst

@nerrad thank you so much for the suggestion! UNfortunately we’ve tried this plugin in the past and, while there were some useful features, it just wasn’t precise enough for us. Thanks again for the suggestion!

@premkumarbsetxt is it the same format, where the first and last name is in the email address?

e.g.
Chelsae Lanham
[email protected]

?

I am going to be experimenting with a script to block this behaviour thanks to a kind suggestion from reddit on how to prevent this.

Solved – the scripts were being blocked by our cookie consent plugin Termly.

Hi! The issue for us was our password manager was autofilling the settings fields and overriding our API keys on page load, so it was a confusing one to debug. Just make sure to disable any form auto-fill and carefully put in the credentials.

Hi Shameem, thanks! That answers the question – appreciated!

Thanks for the reply – that’s great news, will be looking out for that feature release. Thanks for the update.

Managed to get it working however the documentation is very unclear currently with the settings UX changes! No warning that the update would obliterate our settings and reset the API keys!

Hi there, we would like to do the same on our store – do we need to contact support?

Hi there we are having the same console error – how can we fix this?

https://snipboard.io/uXy8qI.jpg

Hi Krystian,

Hope you are well and thanks for the update. We would really prefer not to install yet another plugin on our live site. Is there a fix on the way in a future update of the official plugin? We will wait until this is available.

Best, Jethro.

Hey Krystian,

Hope you are well! Just reporting back here – we have updated to the updated package which you linked to above: Version 2.8.1-alpha1?

We’ve cleared all our caching layers.

I’ve also made sure to include the filter in our functions.php file for our child theme:
add_filter( 'woocommerce.feature-flags.woocommerce_paypal_payments.paylater_configurator_enabled', '__return_false' );

Unfortunately this does not enable the legacy pay-later message section and nothing has changed in the plugin as far as I can see.

Wondering if anyone else can verify it’s not just myself having issues?

Thanks,

Jethro

Hi Krystian,

Hope things are well. Just to let you know I’ve duplicated our site onto a staging website and disabled all plugins and themes leaving just woocommerce, paypal payments and the storefront theme activated. Unfortunately the pay-later admin area still does not save any changes to the settings.

First note the suggested snippet to “Restore Legacy Pay Later Messaging Configurator” does not change anything when I added it to my functions.php file on my basic staging site. The below screenshot is with that snipped enabled in my functions.php file:

In the above screenshot I have disabled “Shop” which is ticked by default. When I press save I see the following:

Says settings have been saved, but the Shop is ticked again. I will also note that the Pay Later messaging when I preview the shop section looks like this:

That’s almost a nice banner worth having, but when I look at the frontend on my shop page I see this:

I can only deduce that something is broken on the Pay Later messaging functionality somewhere.

Kind regards,

Jethro

Just to clirify the issue we are seeing when it comes to filtering the products in our performance max asset group -> listing groups:

As we have multiple top-level categories in woocommerce we get them all coming through randomly depending on the order they appear in the product_type field in our feed:
https://snipboard.io/px6AcR.jpg

Hi Shameem,

Thanks for the response. Is there a timeline for the enhanced conversions functionality to be released?

Many thanks,

Jethro

• This reply was modified 6 months, 1 week ago by jh.