marlonsabala

Thanks @giuse

I had the only caching plugin disabled (litespeed), but ok, I’ll keep an eye on it.

Also, I meant to ask you:

1. what is the biggest advantage would you say of the paid version. The one that is more likely to help us speed up our pages
2. Is there an obvious way of disabling a given plugin globally?

Thanks in advance

Marlon

Thanks for your detailed response.

Well, I tried with the sandboxed site and had no issues there. Then I tried to see if it was a plugin conflict by doing some testing on our staging site but all was working perfectly there.

Then I went back to the live site and the issue remained UNTIL I applied some filters to the Learndash custom post types, and then the 404 error disappeared. No idea to be honest, but it works now ??

I am finding some weird issues where changes made to the post type don’t stick until the filters are applied on an individual page basis. It’s intermitent, so it’s difficult to figure out what might be going on.

Here’s an example: https://vimeo.com/853087543/6e8346f3fa

Any ideas?

Thanks in advance

Marlon

Got it. Ok, I’ll test this out.

Thanks again for your help

However, the sub was not set to manual I don’t think. When I looked at the sub before changing the token, the payment method was still credit card.

Got it.

I guess I could always revert that back if we ever decide to go back to the other plugin, correct?

I’m not tech savvy enough to do this I don’t think. ??

Does this look right to you (https://ibb.co/0YHQYRr), or should I be more specific and filter by meta_key = ?_payment_method too? (not sure how I would do that)

Hi @giuse,

Thanks for the update.

Could you please update me once you have news on this?

Thanks in advance

Marlon

Hi @mrclayton

Thanks for your reply.

So, for that user that paid for the renewal manually after the initial failed payment, the?_payment_method?value was ?stripe. I checked a brand-new sub, and it was?stripe_cc.

Does that help?

Just caught another @mrclayton

Slightly different this one.

User a few days ago goes into the payments section of WC and updates his card. Your plugin shows the correct token on the user page, but sub fails to renew because the token was not updated there.

Sorry about the delay. Been traveling for the last couple of weeks.

So, yeah, that was probably me changing it manually.

But I just spotted this happening again with another user on the live site. Something here is def not right.

So, that user X.

He’s been paying with a given card for the last few months with your plugin, no issues. This month the renewal attempt comes up with the error:

Recurring payment for order failed. Reason: A source must be attached to a customer to be used as a payment_method.

Why would that happen now?

Half an hour later the user goes in and manually pays for the renewal. This should update the Payment Method Token, but it does not. It’s still the old src_blahblah

I then have to go in and manually change it to the new style pm_blahblah which is correctly found both in the user page and on stripe.

No idea why, but I’m catching this more and more.

Any ideas?

Hi @giuse

I appreciate you might be very busy and this might not be a bug you are too worried about fixing. But could you let me know please and I will look elsewhere for a solution.

Thanks in advance. Appreciate all your help thus far

Hi again,

Yes, it’s set to manual renewal payments as that’s what WC does when it detects a staging site.

However, I navigated to the DB and it was already set to “stripe_cc”

Any ideas?

Thanks in advance

Thanks for your message. @mrclayton

So, I followed (I think) your recommendation on our staging site: https://vimeo.com/846303168/18042df80e

Any ideas?

@mrclayton Hope you’re well.

I wonder if you could help. I continue to have issues with the transition to your plugin.

So, I continue to see payments fail with the following error, many months after the initial transition to your plugin: “Recurring payment for order failed. Reason: A source must be attached to a customer to be used as a payment_method.”

It seems that when a renewal payment fails, even if the user comes to the site and updates the payment details on the checkout page in order to pay for the failed renewal, the “Payment Token” field does not get updated. This means the payment will fail again the following month. This will continue until an admin updates the info on the sub page manually.

Should the token not get updated in the sub when the user enters a new payment method?

Let me know

Marlon

never mind, sorted with display: inline; in the <p> tag.

Thanks anyway

HI @giuse ,

Thanks for getting back to me. Sure, let me give you a bit more info…

• Do you see any warning in the FDP top navigation on the right corner?

Nope

• Do you maybe have any blog posts, or other post types with the same slug?

No. But as I alluded to before, the issue is probably connected to the way Learndash handles nested URLs. That is, they offer the option to use the same lesson/topic/quiz in multiple courses. So normally a lesson post would be  https://example-domain.com/lessons/letter-a/ but when added to a given course, it becomes  https://example-domain.com/courses/course-1/lessons/letter-a/ and you have the option to add it to another course, so it would become  https://example-domain.com/courses/course-2/lessons/letter-a/

Interestingly enough, the issue is not there in every single case where this happens. Very strange.

• Have you visited the backend page Settings => Permalinks?

Yep.

• To confirm that, just for testing purposes maybe try to enable Learndash everywhere in the FDP settings, but check the issue every time you do it.

I reset FDP settings. Problem persists.

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