2Checkout not giving "access" to paid subscriptions

[gsk8]

Yes I am and am fairly certain it is listed everywhere on the admincp. Can you tell me if there are any areas I may have forgotten?

[Wayne Luke]

The 2Checkout site. Any service that calls to your site should be updated.

[gsk8]

Everything is https on both ends.

[gsk8]

Here is the final response from 2co tech team

As previously advised the integration with Vbulletin is not tested and documented by us. You will need to contact Vbulletin directly in order for them to assist you with information based on the integration settings developed by them.

[Wayne Luke]

The problem is that the 2CheckOut integration was last updated in 2016. If they have changed their API in any way, there is no way to guarantee that our integration will still work. This is what I tried to say earlier. I have no way of testing this implementation to see if it even works anymore. Since vBulletin 4.X is End of Life, I do not see any updates. I don't know if anyone is using this provider in vBulletin 5. Most of our customers just use Paypal.

IN order to determine the issue, we need to know the point of failure. Seems to be the callback but without error logs from the server and transaction logs from within vBulletin, we cannot find out where this is occuring.

[gsk8]

Can I give you access to both accounts so you nose around?

[gsk8]

Here is what they sent:

We haven't made any updates to the API within the last 2 years.

Please provide the following API documentation to Vbulletin so they can verify if the API system is configured correctly: https://www.2checkout.com/documentation/payment-api/

From our side, we cannot provide exact information as we haven't developed any integration with Vbulletin and we don't hold any information related to the configuration made on their side.

Can you please look under the hood?

[gsk8]

Hey folks, can someone from the staff see the above post and get back with me? I'm bracing for a hurricane and may not have internet access for a few days.

I have been manually giving subscribers a paid subscription who (several times a day) but may not be able to this weekend.

[Wayne Luke]

I'll take a look at it when I can but I can't guarantee a time frame. Technical Support doesn't include code modifications. We won't be able to have developers update the code because vBulletin 4.X is End of Life and does not receive development resources anymore. This means there will be no bug fixes forthcoming from the development team. You'll have to continually marking them for the foreseeable future. You should not this in the description of the paid subscription so your users know what to expect.

[gsk8]

I appreciate that. Just remember, 2CO said they have not made any changes, so I wonder if ever really worked on VB?

[Mark.B]

I appreciate that. Just remember, 2CO said they have not made any changes, so I wonder if ever really worked on VB?

Impossible to say with any certainty unless any other customer can confirm it.

[gsk8]

Well, I just did a quick search and found several pages. Here are several threads that had problems:

https://www.vbulletin.com/forum/foru...-subscriptions

https://www.vbulletin.com/forum/foru...rom-3-8-7-to-4

https://www.vbulletin.com/forum/foru...kout-bug/page3

https://www.vbulletin.com/forum/foru...t-api-problems

https://www.vbulletin.com/forum/foru...-subscriptions

https://www.vbulletin.com/forum/foru...ning-2checkout

[gsk8]

I'm going to try the below edit and see what happens. But it's clear from these posts that this problem has been overlooked for a long time.

https://www.vbulletin.com/forum/foru...t-api-problems

It's not a perfect solution, but it works... just go into your "subscription_payment_2checkout" template and change the line that says

Code:
<input type="hidden" name="cart_order_id" value="$cart" />
(at least that's what I think it says, as far as I can remember... if not, just look for a line with that "cart_order_id" in it)

into something like

Code:
<input type="hidden" name="cart_order_id" value="$bbuserinfo[userid]" />
That should include the userid in all 2checkout confirmation emails (it should look something like "Cart XXX" where XXX is the user id.)

You can also use any of the other user details, like $bbuserinfo[username] or whatever... it sure clears up all the confusion.

[gsk8]

Apparently bug reports were sent in both VB3 and VB4 on this:
https://www.vbulletin.com/forum/foru...ever-be-fixed/

[gsk8]

Well, the above code did not work for the subscription_payment_2checkout template. So I tried something different going off a Paypal line (see bolded red). It didn't work either. I got an error.

I then changed this:

<input type="hidden" name="sid" value="{vb:raw settings.twocheckout_id}" />
<input type="hidden" name="cart_order_id" value="{vb:raw item}" />
<input type="hidden" name="total" value="{vb:raw cost}" />
<input type="hidden" name="id_type" value="2" />
<input type="hidden" name="c_prod" value="{vb:raw subinfo.twocheckout_prodid}" />

to this:

<input type="hidden" name="sid" value="{vb:raw settings.twocheckout_id}" />
<input type="hidden" name="cart_order_id" value="{vb:raw userinfo.username}" />
<input type="hidden" name="total" value="{vb:raw cost}" />
<input type="hidden" name="id_type" value="2" />
<input type="hidden" name="c_prod" value="{vb:raw subinfo.twocheckout_prodid}" />