I’m getting Fatal error! Payment with ref_id swpm_xxxxx can’t be found

[YAL]

However, reloading the page works… the proper objects are created on Stripe’s side, and I end up with a new user on my WordPress website.

I’m on the default WordPress theme. I’ve also tried deactivating all the other plugins, it made no difference. I’m baffled.

Thanks.

[The Assurer]

Please enable the debug logs for SWPM and post the results, when the error occurs. Also, please ensure that you are running the latest downloadable version of SWPM. Finally, are you using any caching plugins?

[admin]

The most frequent reason for issues with Stripe subscription payment buttons often stems from an incomplete webhook configuration in your Stripe account. To ensure your webhooks are set up correctly, please consult the ‘Troubleshooting Section’ of our documentation. This section provides detailed steps to verify your webhook setup:

https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/#troubleshooting-related

[YAL]

I somehow landed on the legacy version of instructions for creating the button, so my webhook was not set to the right events. I’m no longer getting the error that I did.

I tested with my admin password, and I saw in the logs that it was trying to update the membership level of my admin user:

[2024/01/31 20:59:44] – SUCCESS: Updating the current membership level (5) of this member to the newly paid level (5)
[2024/01/31 20:59:44] – SUCCESS: swpm_membership_level_changed action triggered. Member ID: 15, Old Level: 5, New Level: 5
[2024/01/31 20:59:44] – SUCCESS: The to (Level ID: 5) and from (Level ID: 5) values are the same. Nothing to do here.

Unfortunately, there seems to be a problem with this code because WordPress said there was a critical error, but I was not able to figure out where exactly.

When I tested with a *NEW* user, everything ran fine, so I’m going to mark this as “fixed” but see the problem above if an existing user tries to get an additional subscription.

[admin]

The critical error message can be sometimes little bit misleading. Reset the error_log file of the site. Also reset the debug log file of the plugin. Then test out various functionality of the site to see if you have any new errors being generated. If not, then everything is likely working fine at the moment.

[Author]

Posts