Renewals Fail
-
Hi there, we are facing a problem with renewals in our shop. It’s a Woo Subscriptions shop. We are running an older WP because of a revision in theme. but all plugins are up to date.
Every order is getting this message.
Kon geen iDEAL betalingshernieuwing aanmaken. [2021-04-25T11:38:11+0000] The customer () could not be used or found. [2021-04-25T11:38:11+0000] Invalid resource id. Bestellingsstatus gewijzigd van Wachtend op betaling naar Mislukt.
Can you tell us how to get this to work again?
The page I need help with: [log in to see the link]
-
Hi @dreampress,
There was a bug in Mollie version 6.2 causing some metadata to be missing for new subscriptions, which is responsible for the issue when creating a renewal. Our next plugin update 6.3 should automatically resolve these issues.
Please update the plugin to the latest version 6.2.2 if you have not yet done so.In the meantime, this SQL query can be used to repair the affected subscriptions:
https://pastebin.com/MwBvqKTu
Please create a new database backup before running any SQL queries.
This query automatically creates the missing _mollie_customer_id meta keys in the wp_postmeta table and repairs the renewal functionality.
You only need to run it once and you will then be able to create renewals again.
Apologies for the inconvenience.
If there are any questions regarding the query, please let us know.Kind regards,
NiklasThanks… we’ll try to run the query asap.
Ok, Niklas, done that. But how do we adjust the table prefix in your script to the one we have for the site? And is this a safe thing to do?
If you use a custom table prefix, then you will need to change the table names in the query:
Thewp_
part in thiswp_posts
(used once) and thiswp_postmeta
(used three times) table would need to be replaced with your own table prefix.The query is very specific in what it does and we successfully tested it across many different systems. But before you make any changes directly to your database, it is always recommended to create a new backup beforehand, just in case.
Our next update 6.3 will automatically fix the issue, without the need to touch your database at all. But it will likely take a few more days before it can be released.
Kind regards,
NiklasHi,
When I run the query I get the following error: #1044 – Access denied for user <user> to database ‘information_schema’.
I am not an expert in MySQL, can you explain in detail how to implement this fix? I did already backup the database.
Thanks
EDIT: I think I made it work, it said it returned 0 rows though, is that correct?
-
This reply was modified 4 years, 1 month ago by
arthurnoort.
Hi @arthurnoort,
I am not sure about the exact response as it may vary.
But here is an example of how to do it with phpmyadmin.But if you can find the
_mollie_customer_id
in yourwp_postmeta
table for the corresponding subscription post ID, then it did succeed.
If you reactivate the subscription and create a new renewal, then it should work as usual.Kind regards,
NiklasHi Niklas,
Thanks for your reply. I have followed the instructions but the _mollie_customer_id is not updated, it’s still empty. I tried zeroing in on what part of the query is responsible for returning 0 rows, turns out it’s the pms.meta_value is NULL; part in the WHERE clause. When I remove that part I do get a table of the order IDs and the corresponding customer IDs.
Is it safe to run the procedure without that pms.meta_value is NULL; part?
Thanks
-
This reply was modified 4 years, 1 month ago by
arthurnoort.
-
This reply was modified 4 years, 1 month ago by
arthurnoort.
Hi @arthurnoort,
When there are any issues with the query, please open a support ticket with us as described here:
https://mollie.inpsyde.com/docs/how-to-request-support-via-website-widget/
Please include a link to this thread.
We’ll get in touch with more information. Thanks!Kind regards,
NiklasHi Niklas,
Sorry for the spam, see my updated response:
I tried zeroing in on what part of the query is responsible for returning 0 rows, turns out itβs the pms.meta_value is NULL; part in the WHERE clause. When I remove that part I do get a table of the order IDs and the corresponding customer IDs.
Is it safe to run the procedure without that pms.meta_value is NULL; part?
Hi, I have the exact same problem with missing ID’s. Unfortunately, the pastebin link is not working. Could you share the SQL query again?
And question nr2: what is the ATA of the 6.3 version that should fix the problem automatically?
Hi @dreampress, @arthurnoort & @timoroosendaal,
Our update 6.3.0 has just been released and it includes an automatic fix for the missing meta data.
Apologies for the delay, there were a couple of things that had to be included in this release.
Please update the plugin to automatically repair all affected subscriptions.
If any issues remain, please open a support ticket with us as described here:
https://mollie.inpsyde.com/docs/how-to-request-support-via-website-widget/
We can help you faster with a ticket in our own support system than on the forums.
In any case, we are interested in your feedback. Thanks!Kind regards,
NiklasGreat work! The update has been done yesterday. We are keeping an eye on the orders.
Many thanks for the fix.
Nice! Just tested and pushed the update to live. Looks like all went well and missing ID’s are back in the DB. Thanks for the quick update and responses π
-
This reply was modified 4 years, 1 month ago by
- The topic ‘Renewals Fail’ is closed to new replies.