Hello @misterneil2023
Thank you for reaching out to us, we are here to help.
The hosted fields issue is a problem that requires a bit more complex solution. In order to get this resolved, we have to get the new Vault_v3 API implemented first, and this is expected in Q3 (but no specific release has been assigned to this). At this time, we can upgrade to new hosted card fields, which should resolve the issue.
There is the expectation that this will all be done with release 2.4.2, but we can’t be sure until these changes get tested and verified. Since we had some delays on this bug, I am a bit hesitant to confirm any date/release, so I can only give you an expectation.
Please let me know if this answers your question.
Kind regards,
Joost
Hello there,
quick update: we were not confident enough to release the vault_v3 update for our next release, so the 2.4.2 release will not include this. We will try to include for the release after that, but it all depends on next development tasks and testing in order to confirm this. Our apologies for the delay.
Kind regards,
Joost
Hello @misterneil2023,
I just checked the status of the hosted fields improvement, and it looks like this improvement will only be included with release 2.5.0. This release is expected to become available in January 2024.
Kind regards,
Joost
We haven’t heard back from you in a while, so I’ll mark this thread as resolved.
I have been waiting to hear from Joost van de Vijver to find out if version 2.5.0 of the plugin resolves the issue. As far as I know in my testing, the current plugin still produces the error message. Please keep this thread live.
As far as I know in my testing, the current plugin still produces the error message.
The message is present across all plugin versions because it is not a plugin issue. It is caused by a limitation with PayPal’s hosted fields not working well with the way WooCommerce behaves on the shortcode checkout page (AJAX reloads destroying the entire payment method section incl. the card fields).
PayPal Payments update 2.5.0 in mid-January introduces a new version of PayPal’s card fields which resolves this message: https://github.com/woocommerce/woocommerce-paypal-payments/issues/1011#issuecomment-1834207391
But as long as the current hosted fields implementation is used, the message will occur when the card fields are destroyed by an AJX reload, and there isn’t anything we can do about it on the plugin level.
Kind regards,
Niklas
What has caused Ajax to behave this way now? Were changes made to it?Ajax was working before.
Hello, I am following up to ask, has the hosted fields issue been resolved with the latest version of WooCommerce PayPal Payments v2.5.1?
Hello @misterneil2023,
You are correct, this issue should have been resolved with the 2.5.0 release, but there was a big issue with this release, so we pushed the older release (2.4.3) out again to minimize the damage that this could have done. So at the moment the 2.5.1 release is an old release, but we are testing the 2.5.2 release, that should be similar to the 2.5.1 release, but without the failures we isolated after release.
If you want, you could test the beta release we have currently available here, but I believe the official release should take place this week (if not today), so it might be worth waiting for this one. Sorry for the confusion this might have caused.
Kind regards,
Joost
