Subscription ID is null - Merchant Managed Subscription..

Hello,
After through testing found the bug was the missing access check for the subscription entities. I added a Merge Request for the change.

Let me know if there is any changes needed.

Reference: https://www.drupal.org/node/3201242 →

Unassigning for review thank you.

krystalcode → closed merge request !4

Thanks for the contribution.

I closed your MR since I wanted to merge this through 1.x that I have not removed from the releases yet, so that the fix gets there as well. The code, together with some more improvements/fixes, is on the latest 2.x. You should still get credit when the issue is marked as Fixed.

I will make a release and mark this as Fixed together with 🐛 Refund IPNs fail due to amount formatting Active and 📌 Restructure IPN processing code Active , once the latter are tested. If you are nevertheless able to test this issue on the latest 2.x, that would be great. I don't have an application with subscriptions at the moment to test this, even though the code is straigh-forward.

Hello,
I do have a Drupal project with Subscriptions I can run the tests on. A few months back Bluesnap had issues with their Sandbox. We ended up turning this off for the time being.
I can setup a stage version and add the latest 2.x version and run some tests.

We did get this email from Bluesnap back in Feb about updating their SDK:

I'm getting back to you with some updates after discussing this with our Product team and explaining that you use the Drupal plugin to integrate with us.
While we see that everything works as it should with your integration (transactions are successfully processed) - we are still uncertain that all of the actions involving Drupal are done using the most recent Web SDK version.
The Drupal integration was not built/commissioned by BlueSnap - it was created by one of our partners back in 2020, and we do not know what updates or changes have happened with the Drupal open source since. The same goes with the PHP SDK - it was last updated back in 2018 and it seems to be outdated.
I'm on the fence here because I know that you put a lot of effort into this integration - but at the same time, since BlueSnap does not support nor maintain the Drupal integration, we cannot guarantee that your application will work smoothly after March 1st.
What I would suggest for you to do next is to contact the Drupal 'Maintainers' of the BlueSnap project:
https://www.drupal.org/project/commerce_bluesnap →
and ask them these questions:
Can they confirm that the plugin is using the most recent Web SDK version, as described in the BlueSnap documentation: https://support.bluesnap.com/docs/version-upgrade-faqs#v40-to-v50
Can they confirm that the Plugin fully supports 3D Secure - because the initial launch did not support it (5 years ago); https://support.bluesnap.com/docs/3d-secure
Unless you get a clear 'Yes' on both questions - I think that it may be a good idea to consider another integration.
I apologize for not providing better news, I hope that this information is helpful, at least.

---------

I will try to get on the tests this weekend!

Thank you for the message!!

Hello,
There was a delay due to the fact the site did not have a Stage URL that the Bluesnap Webhook could access. We finally got a stage site for testing.
I ran the test after using this version "composer require 'drupal/commerce_bluesnap:2.x-dev@dev'"
I setup a Recurring One hour product and Commerce Recurring is working fine on the Production site. I am using the Bluesnap Sandbox.
It is working and the Payments are recurring (yippy).

One thing have noticed since Bluesnap had issues is the Webhooks (IPNs) area has changed: https://sandbox.bluesnap.com/jsp/webhooks_configuration.jsp (need an account).

I did notice this in the error logs (the Bluesnap SDK):

Message Deprecated function: Creation of dynamic property Bluesnap\Models\CreditCardInfo::$issuingCountryCode is deprecated in Bluesnap\Models\Model->__construct() (line 41 of /public_html/vendor/shabananavas/php-bluesnap-sdk/src/Bluesnap/Models/Model.php)

This is due to their changes to their SDK back in Feb.

I am very happy finally the tests work.

Have a good day and thanks for the help.

chris