Fixed PayPal assigning wrong upgrade name and not working

Chris D said:
I would at least try to see if PayPal can redeem themselves by doing anything here.
Click to expand...
I thought I was onto something.

In PayPal I can disable the subscription plans (Subscriptions >> Subscription plans (list) >> Disable). They all have 0 subscribers because they were created by the new API which isn't being used yet due to this bug. So I went ahead and disabled them all. Then I created a new upgrade in XF. However even with a NEWLY created upgrade, I get:

"Oops! We ran into some problems.
Failed to create PayPal order: The requested action could not be performed, semantically incorrect, or failed business validation."

UNLESS I change the price. The price seems to be the triggering factor here when combined with the subscription length and recurring billing. It's also fine if I turn recurring off or change the length. But once it has the combo of the product that was listed incorrectly it thinks it's the same even if you create a new one. So disabling the wrong product (not the new one) causes this error and enabling it again causes that wrong name to show for this newly created product (upgrade). 🤷‍♂️
 
Last edited:
PayPal was not very helpful. Deleting a subscription plan is not possible only disabling it (but apparently it used to be an option). The fact that XF is recognizing the wrong plan based on parameters, the blame was placed back to XF and the API call. 🤷‍♂️ Makes me want to use a different PP account but that seems excessive.
 
I’ll do some more testing in this release cycle and try to come up with some solutions.

I wouldn’t say it’s worth the hassle of trying new accounts etc.

We’ll see if there is anything we can do with the API. Maybe we can force the creation of a new product if there is a mismatch between what we have and what the API is saying.

Legacy PayPal is at least a reliable solution for now.
 
Also this is only an issue with recurring billing. If I turn it off it works and the product name is correct, but this is because there is nothing to conflict with in PP since plans are stored under Subscriptions and I guess one-offs are not (or stored elsewhere). FYI I used a tech support ticket to try to get them to delete the plans from my account since they have 0 subscribers and were created via API with the previous bug. I hope they can and will let you know if that addresses this.
 
Well, I tried, After a very detailed ticket with links to this bug and steps, they won't delete them, and if I am seeing the wrong plan their solution is:

If you are seeing an incorrect plan on your website, you will need to remove the button details from the website where the buttons are displayed. This can be done by contacting your website developer.

I'll have to wait to see if XF can address as I have exhausted the PP route including recreating the payment profile and user upgrade on XF, and using fresh API creds. Still, it will want to associate with the wrong plan.

Thanks
 
beerForo said:
Well, I tried, After a very detailed ticket with links to this bug and steps, they won't delete them, and if I am seeing the wrong plan their solution is:

If you are seeing an incorrect plan on your website, you will need to remove the button details from the website where the buttons are displayed. This can be done by contacting your website developer.

I'll have to wait to see if XF can address as I have exhausted the PP route including recreating the payment profile and user upgrade on XF, and using fresh API creds. Still, it will want to associate with the wrong plan.

Thanks
Click to expand...
Working with PP supporr is useless. It can be one of the most infuriating obstacles to overcome.
 
Last edited:
Need to add one more note. Editing the name or price on the paypal side does not fix this. So the original issue was it was showing the wrong $5 plan (other site name's plan for $5), if I go to that plan on the PP end and rename it some gibberish and put $9999, that's what shows when you click it from XF where it still shows $5/month. So something is connecting these plans and it is the price on the XF end, but on the PP end it just keeps going to it no matter what like it's coded somewhere. Perhaps the ID code? Thanks
philmckrackon said:
Working with PP supporr is useless. It can be one of the most infuriating obstacles to overcome.
Click to expand...
Yup
 
Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.3.6).

Change log:
Attempt to sync PayPal REST API with current product name.
Click to expand...
There may be a delay before changes are rolled out to the XenForo Community.
 
Chris D said:
My best idea at this point is seeing if we can routinely synchronise the current upgrade settings across, including the name, but I'm not even sure at that point if this is possible.
Click to expand...
Was just reminded about this post and I wanted to point out that completely in line with my scathing retelling of my experiences with PayPal that, yes, it is possible to update the name, but it's basically undocumented so that's good, I guess.
 
Chris D said:
Had a chance to look into this yet @beerForo? Hopefully it should be a little more in sync now.
Click to expand...
I was on Legacy so didn't try until today. Same error. If I change my gateway to the new PP it works fine unless I change the price (which is what I want to do) and I get this:

Oops! We ran into some problems.
Failed to create PayPal order: The requested action could not be performed, semantically incorrect, or failed business validation.

Only happens if you change the price, keeping it the same and using the new gateway, it works.
 
Last edited:
So I can change the price AND the length and it works. The error is generated when keeping the same length (yearly) and changing the price.

$xx for 12 months works but not 1 year (current setting). I could use it like that but I'd rater fix it and have it say a year.
 
@Chris D seems to be due to it not finding the plan in PP due to this one being marked Inactive. Not sure why it would not create a new plan but marking Active on this one in PP allows it to find and edit it. Must have been a testing one used with the same parameters and it needs it to be on since it it trying to match it, but it was Inactive due to having the original bug (I guess). PP is really frustrating.

(However the name of the plan/product is still not appearing with Recurring off. But you do get the checkout page and price. In the old gateway it has a dropdown menu under the price that has the plan/product name.)

That's all for now, have not tried to go live. 😆 Will update. Thanks!

EDIT: Yes, if XF created a plan in PP for a certain price with recurring on, and that plan is marked Inactive in PP itself, even if the price is different, as in, edited on the PP end, it will throw this error. It seems to want to find the plan that was originally created with those parameters even though they no longer match. So if you do testing like I did, and have plans you turned off due to the testing creating multiple subscriptions you think are not needed, best practice: just keep them active even if they were tests or you may run into this.
Chris D said:
Had a chance to look into this yet @beerForo? Hopefully it should be a little more in sync now.
Click to expand...
I think so! 😂 Except how non-subscriptions (one-time payments) do not show product info.
 
Last edited:

Similar threads

X
Expiring recurring user upgrade should explicitly cancel with payment provider and not assume failure
Replies
1
Views
300
Xon
X
Liam W
  • Question Question
XF 1.5 Spam cleaner using loads of memory and not working...?
Replies
2
Views
434
Liam W
Liam W
Back
Top Bottom