Massimo

Hi,

Yes, the latest update (7.0.13) fixed the issue.

Thank you!

• This reply was modified 4 months, 3 weeks ago by Massimo.

Hi,

I updated to the latest version and the issue is still there.

Did you have a change to give it a look?

Thanks

Ho notato la stessa cosa.
Prova ad aggiungere questo CSS

.woocommerce-checkout li.wc_payment_method label img {
height:2rem; /* puoi usare valori in px se preferisci */
width: auto;
}

per modificare solo il logo Satispay:

.woocommerce-checkout li.wc_payment_method.payment_method_satispay { ... }

Ciao

ENGLISH

I noticed the same thing.
Try adding this CSS:

.woocommerce-checkout li.wc_payment_method label img {
height:2rem; /* you can use px values if you prefer */
width: auto;
}

To edit only the Satispay logo:

.woocommerce-checkout liwc_payment_method.payment_method_satispay { ... }

Thank you for the fast reply.

Yes to both, and double-checked in case something changed during the update.

Hi,

I suspect ... WordPress Admin > Settings > General your Site Address option is missing the locale portion of the url

Yes, and that is the expected behaviour.

When I echo home_url() the url is correct and includes /en/.

Thank you for the link in your reply!!

Looking at the source code, I saw on line 843:

$api_request_url = trailingslashit( home_url( '/wc-api/' . $request, $scheme ) );

This is where the issue occurs! Looks like the path you set in ‘ ‘ overrides the url set by Polylang. However, you added a filter on line 851 (great!)

apply_filters( 'woocommerce_api_request_url', $api_request_url, $request, $ssl )

So here’s a little snippet that adds the language slug to the url:

function ppl_api_request_url($api_request_url, $request, $ssl) {
    $ppl_url = trailingslashit( home_url('/'.pll_current_language().'/wc-api/' . $request, $scheme ) );

    return $ppl_url;
}

add_filter('woocommerce_api_request_url', 'ppl_api_request_url', 10, 3);

Tested and works!

Thank you again for your help and support!

• This reply was modified 11 months, 3 weeks ago by Massimo.

Hi,

Thank you for your support.

Maybe I found the issue.

I use Polylang as the site is in multiple languages.

The URL is set to include the language, e.g.:
https://www.mysite.com/en/
https://www.mysite.com/fr/

Say that I am on the /en/ page, after paying with PayPal the return URL is now:

https://www.mysite.com/wc-api/ppcp_order_return/?order_id=9132…

the /en/ is missing, that’s why I land on the 404.

If I add it manually from the 404-page, then it works as expected.

Now, how can I fix this?

Thank you!

Thank you. Yes, I confirm that on a clean install all works…however I can’t find which plugin is interfering with wc-api.

I am only using your payment plugins –Stripe (which works) and Paypal.

I disabled most of the plugins and I still et 404.

If you have an idea on how I could debug this, please let me know. I’ll keep trying and update this post if/when I find the issue.

Hi, thank you for the prompt reply.

Yes, I see them. I just did not add them for readability (I paste it below, replacing the data with xxx). The order_id is correct.

wc-api/ppcp_order_return/?order_id=xxx&order_key=wc_order_xxxxx&payment_method=ppcp&token=xxx&PayerID=xxxx

WooCommerce version 8.3.1

• This reply was modified 11 months, 4 weeks ago by Massimo.

Thank you for your reply! I patched it myself. All good!

Hola Roberto,

To create the translations button is not very difficult:

There are 2 functions that you need to check against the $postID: pll_get_post_language and pll_get_post_translations

With those functions, you can check which language version is available.

To create a Polylang translate button which links to the original, you have to create a Polylang nonce. This nonce is specific to Polylang and won’t work without it.

$nonce_url = wp_nonce_url( $url, 'new-post-translation' );

$url = '/wp-admin/post-new.php?post_type=YOURCPT&from_post='.$postID.'&new_lang='.$language_to_translate_to;

Hope this helps.

• This reply was modified 2 years, 4 months ago by Massimo.
• This reply was modified 2 years, 4 months ago by Massimo.
• This reply was modified 2 years, 4 months ago by Massimo.

Hi Andrew,

I did contact Braintree before asking here (in the deleted thread). Below you’ll find their answer which is from 27 March 2018.

Hi Massimo,

Thanks for reaching out, happy to be of help.

After looking at your integration, it looks like this value is being passed to the Braintree gateway: |*fail_on_duplicate_payment_method=>true*|.

It would be my guess that when WooCommerce’s trial activation happens it’s calling on a duplicated payment method which in turn is setting off the above command to make it fail.

There are currently two options available for handling this situation:

* You could simply delete this original record and then re-attempt!
Since there would be no duplicate, they would then be successful.
To do this, search for the customer
<https://articles.braintreepayments.com/control-panel/search&gt; and
click on their Customer ID to delete.

* Since you’re using WooCommerce I recommend reaching out to the
developer of your plugin to determine how to remove this option
altogether, as activating the trial period on that plugin seems to
affect it.

I hope this helps! Please let me know if I may be of further assistance.

if I delete the user it works though it should work also without deleting the user as then it would not be possible to share a credit card among family or friends.

Thanks for your help.
Max

• This reply was modified 6 years, 7 months ago by Massimo.

Hello,

I have a similar problem. Could you post a solution if you found one?
Thanks for your help. -Massimo