marlonsabala

Hi @giuse

Any update on this?

Thanks in advance

HI @giuse

Apologies for the delay in getting back to you.

So, I did some testing this morning. I think I have a hunch on this.

So, no, I had no rules for those pages and the URL ends up in a 404 even when typed directly into the address bar.

So here’s what I think might be at play. These are Learndash pages. Specifically, lesson pages nested inside specific courses.

Now, Learndash uses nested URLs. Here’s their explanation:

This option will restructure Lesson, Topic and Quiz URLs so they are nested hierarchically within the Chapter URL.
For example instead of the default topic URL https://example-domain.com/topic/topic-slug the nested URL would be https://example-domain.com/courses/course-slug/lessons/lesson-slug/topic/topic-slug

The nesting as far as I can see will be applied to topics, lessons and quizzes. In this case the URL was https://example-domain.com/courses/chapter-2/lessons/letter-a/

Any idea how we might be able to fix this?

I’m keen on getting this plugin applied to our whole site, but will hold off until we can find a resolution here.

Thanks in advance

While I have your attention ??…

I’m trying to figure out a way of whitelisting a certain plugin. So it only loads on page A or B. What would be the best way of achieving the current UI?

Thanks in advance

• This reply was modified 1 year, 9 months ago by marlonsabala.

You got it!

Thank you so much!

Sure thing. So:

1. go to the sub page and click on pencil icon next the “billing” header.
2. Update the “Payment Method Token” with the correct one for that user. This can be found in the User page or in Stripe. It starts with “src_”
3. Now delete the pending order that failed.
4. Create a new pending order. This is done from the “Subscription Actions” box in the main sub page.
5. Finally, navigate to the new order page and under “Order Actions” manually renew.

All done!

Got it. Never knew that was there.

Ok, the solution is (in case someone faces this issue):

EITHER

Log in as the user and checkout with the saved card (if the correct customer token is present in the user page – you can get this from stripe.com or the subscription information). This will update future renewals.

OR

Go to the sub, update the token info. Then delete the failed order, create a new pending order and attempt to charge.

Thank you very much

Marlon

It turns out that if I log in as the user and go through the payment process manually it fixes this.

Nice! Well. Yep it up. It’s a great plugin.

Ok, as suspected, most renewals are going through fine, but I have seen a couple of issues.

So, some users subs failed to renew. The error was something like this:

Recurring payment for order failed. Reason: No such PaymentMethod: ‘src_1GofjuDYhZwnEXXXXXXXX’

Looking at the user page on the backend, I noticed that there was no stripe ID, so I updated that. Still did not work. Same error message.

I noticed that the stripe payment token did not reflect the one listed on the user page (stored in Stripe), so I went into the DB and updated the table wp_woocommerce_payment_tokens see: https://ibb.co/hFpDBXB

No luck. When I attempt to charge the user, it still shows: Recurring payment for order failed. Reason: No such PaymentMethod: ‘src_1GofjuDYhZwnEXXXXXXXX’ (with the incorrect token)

Any ideas?

Thanks for the prompt reply.

Strange. The cards were not showing up on the staging site, but do on the live site. This was a test user with really old cards so perhaps the tokens had been disconnected from Stripe but still showing up in the old plugin history.

Not sure.

Anyway, I’ve made the switch. Let’s see how this goes.

I have a question of I may: keeping this plugin updated takes time and effort, and this is free. How do you get paid for your work?

Marlon

Should this be on? I’ve never had it on before.

https://ibb.co/803RKMR

Hi there @contremaitre

I’m seeing the same thing. Recently, we’ve had lots of failed initial payments on subscriptions. Especially with cards issued in the EU (but maybe this is a coincidence).

We’re losing customers and I can’t figure out why. This is almost always down to the same authentication problem you described.

Any news on this? Was a solution found?

Thanks in advance

Hi again,

First of all, I’m happy it does ??

I only saw references to “credit” cards everywhere on the plug-in. Even the default label in the stripe gateway settings says “credit cards” whereas the woo plug-in says credit/debit cards.

As a customer I would not assume the store accepts debit cards if the label said only “credit cards”. At least for someone living in Europe.

Either way, I’m glad it does accept it ??

One question: We use trial periods and temporary discounts (so the recurring payment can change after X number of months). Does that sort of thing work with Apple Pay?

And a final question if I may: what is the motivation behind the creation of this plug-in? Is this supported by Stripe itself?

Don’t get me wrong, I think this is excellent and I’m really considering a move from the Woo one, but since I don’t see an upsell anywhere and the plug-in seems so well maintained, I’m wondering what is the motivation?

Thanks in advance

Thank you very much,

This does look like a great plugin. I did play with it a little on my staging site.
Unfortunately, it doesn’t seem to support debit cards. Did I get that right?

2.0, that has a nice ring to it.

Amazing work Nick. Thanks so much.

Let me know please once this is out.

Ah yea, fantastic!

I added some text to the email footer using the buddyboss email customizer and that did the trick.

In case someone is looking for a similar solution, here is the code.

// Filter out Buddyboss emails so they don't get stylised by plugin WordPress Email Template Designer - WP HTML Mail
add_filter( 'haet_mail_use_template', 'customize_template_usage', 10, 2 );
function customize_template_usage( $use_template, $mail ){
    if( strpos($mail['message'], '(and Marlon too)') )
        return false;
    return $use_template;
}

Thanks again Hannes