Syde Joost

Hello,

Since we have not heard back from you for over a month, we will mark this thread as resolved. Do not hesitate to open a new thread if you still need our support on this or any other issue.

Kind regards,
Joost

Hello,

Since we have not heard back from you for over a month, we will mark this thread as resolved. Do not hesitate to open a new thread if you still need our support on this or any other issue.

Kind regards,
Joost

Hello @alexliii

sorry for the wait, we have to take a closer look at this, as it seems we made changes that broke this filter. I got some new option for you to try

1. Downgrade PCP to version 2.6.0
2. Add the filter (which caused the error for you earlier)
3. Then disable all Pay Later messaging locations on the Pay Later tab
4. remove the filter
5. update plugin again to latest version

Can you try this and let us know if this option does work out?

Kind regards,
Joost

Hello @alexliii

This is the link you need:?Disable Pay Later messaging Configurator in 2.6.0+

add_filter( 'woocommerce.feature-flags.woocommerce_paypal_payments.paylater_configurator_enabled', '__return_false' );

2# Will the error be fixed natively in the next update? or should we always use the method of the above code snippet?

You are seeing this message because your store is not configured correctly. Your WooCommerce store location is configured with a Pay Later supported region, but the actual PayPal merchant account doesn’t support it. Currently, there is a 1:1 relationship here, as the plugin is not capable of understanding if the connected merchant is eligible. When the store is configured with a Pay Later supported region, the plugin automatically defaults them on. You must first disable the configurator, as otherwise you cannot disable it in the plugin!

I hope this answers your question.

Kind regards,
Joost

Hello @alexliii

We’ve further investigated this and we believe that, on the plugin level the Pay Later messaging is enabled but the merchant account is not eligible for Pay Later features.
To disable this, you would need to first disable the Pay Later messaging configurator with this code snippet:?https://github.com/woocommerce/woocommerce-paypal-payments/wiki/Actions-and-Filters#disable-pay-later-messaging-configurator-in-260
Then you can disable the Pay Later messaging in the Pay Later tab which should resolve these messages in the frontend.

Please have a look and let us know if this helped you resolve the issue.

Kind regards,
Joost

Hello?@gferguson78

Thank you for reaching out to us, we are here to help.

We had already identified this issue and our developers have been working on this issue yesterday. A temporary fix is available for this problem. If you want, you can download the package via?this link, or you can wait for the next release where it should also be included (could be released as early as next week).

If you choose to use the linked package, we will be happy to hear back from you with any positive or negative experiences.

Kind regards,
Joost

Hello @alexliii,

thank you for reach out to us, we are here to help.

This error looks like it is related to server authorizations that might be implemented, not so much any setting of the plugin. I do not think there is much that can be done from the plugin’s perspective.

Can you tell me what the outcome is of this error being shown? Is there any functionality of the plugin that is not working as intended? If that is the case, we could see what we can do. If not, I am not sure how to correct an access issue like this via our plugin.

Let me know what you think about this.

Kind regards,
Joost

Hello @philmusichorus

Our developers have been working yesterday on this issue and already have a temporary fix available for this problem.
If you want, you can download the package via?this link, or you can wait for the next release where it should also be included (could be released as early as next week).

If you choose to use the linked package, we will be happy to hear back from you with any positive or negative experiences.

Kind regards,
Joost

Hello @philmusichorus

Thank you for reaching out to us, we are here to help.

I believe you have also opened a tread via the WooCommerce support pages. As we informed there, you can currently use version 2.7.0 to avoid this situation. We have opened a bug for this that is currently being investigated by a developer. We currently expect a fix to be added in the release that should become available on the 10th of June (we cannot confirm this date).

Furthermore, we have linked this report to the bug, so will update this thread, when a fix becomes available.

Kind regards,
Joost

Hello @koningsvh

if the situation changes, we will have this thread linked to the feature request and update you accordingly. Thank you for understanding.

Kind regards,
Joost

Hello @koningsvh

we have reviewed this request in our backlog meeting, and unfortunately I have to let you know that we have noted their feature request and will revisit it in the future. But for now, there is no easy & clean solution. This request needs to be reviewed again at a later time with PayPal to see if development can be authorized.

For now, there is unfortunately not much we can do to help you with this situation. I am sorry I could not get you a better response than this.

Kind regards,
Joost

Hello @emiver

Thank you for reaching out to us, we are here to help.

In order to help you out, we will need more details than what you provided. The error message you provided probably is not the cause of a failure in stock updates, because this is referring to image validation.

In order to investigate this issue, you probably need to test stock updates manually and in what situation the stock changes are not going through. Also you would need to verify if it is occurring for all products or only for some?

You may want to perform a full conflict test to rule out eventual issues with the theme or a different plugin. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for?WooCommerce and?PayPal Payments to see if the behavior persists. Here’s a guide that explains the steps in more detail: How to test for conflicts.

We do have a FAQ items available for a similar situation that you probably also should take a look at. You can find it here.

If you need more support and need to share more details (full logs, screenshots) with us, you can also open a private engagement, by following these instructions.

Kind regards,
Joost

Hello @koningsvh

that is not a problem, I have opened a request for this feature and will try to see if there is no filter that we can create/provide for a quick turnaround.

However, the implementation of such a feature, might take more time than you would be willing to wait. The last update of our plugin, was 5 months ago and not much time has been given to add updates in the near future. Currently, we mostly do updates for compliance and security. I am adding this, just to set the right expectations.

I will let you know when I get more details on the bug or if I possibly get the filter for this.

Kind regards,
Joost

Hello @koningsvh

Thank you for reaching out to us, we are here to help.

There is unfortunately no such option, you can only disable the sync in both ways via the WooCommerce product settings, but this is probably not what you are looking for. The only option I see is to no use the WMS function (if that is possible)?

Kind regards,
Joost

Hello,

It has been quite some time since our last communication, so we will mark this thread as resolved. Please open a private engagement via this link if you are still facing issues or have questions that you need us to answer.

Kind regards,
Joost