Hi, I’m sorry to hear about your issue. It is not possible for the plugin to have caused data loss – as there are no mechanisms for it to delete data from the database, or delete files or other plugins such as WooCommerce. Perhaps you or your hosts have disabled Woocommerce as a plugin? Your data will still be in the database if this is the case. I’m concerned that there is something else at play here as a result – but can you please confirm what the fatal error was? Your hosts will be able to provide this from the php error log. We’re keen to help. Thanks.
@kadament
here is the log. This is the error from the time my website went down, only getting it back when disabling the GoCardless plugin.
WooCommerce was not deleted rather disappeared. When trying to reactivate WooCommerce it was nowhere to be found in the Plugins from the WPadmin.
I was unable to install woocommerce due to a message- Installation failed: Destination folder already exists.
this morning i have accessed the files via Filezilla, i went in and found the woocommerce file. i had to rename the file and then install a new woocommerce file. i now have everything back.
My host have told me not to reactivate this GoCardless Plugin and i should delete it altogether?
as i said at first i was extremely impressed with your plug in.
2023-03-13T17:41:03+00:00 CRITICAL Uncaught Error: Typed property gc_ob_wc_gateway::$gatewayGocardless must not be accessed before initialization in /homepages/37/d4295971963/htdocs/wordpress/wp-content/plugins/wc-gocardless-instant-bank-payments/wc-gocardless-instant-bank-payments.php:173
Stack trace:
#0 /homepages/37/d4295971963/htdocs/wordpress/wp-includes/class-wp-hook.php(308): gc_ob_wc_gateway->initBillingRequestController('')
#1 /homepages/37/d4295971963/htdocs/wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
#2 /homepages/37/d4295971963/htdocs/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#3 /homepages/37/d4295971963/htdocs/wordpress/wp-admin/admin-ajax.php(203): do_action('wp_ajax_nopriv_...')
#4 {main}
<span style="background-color: rgb(238, 238, 238); color: rgb(60, 67, 74); font-family: monospace; font-size: 13px;"> thrown in /homepages/37/d4295971963/htdocs/wordpress/wp-content/plugins/wc-gocardless-instant-bank-payments/wc-gocardless-instant-bank-payments.php on line 173</span>
Thanks for this, good to hear that there wasn’t any data loss. In terms of the error – we need to get to the bottom of why this has occurred of course, but this error has been thrown at the point someone has tried to make a payment, and will only effect that individual user’s session. This error will not have taken your site down for all users, so you can safely re-enable the plugin, but disable the payment gateway in the WooCommerce payments area to stop it being an available option for customers until the issue is resolved.
Can you please confirm which php version you are using? This can be found at your domain /wp-admin/admin.php?page=wc-status under the ‘server environment’ section. You said that it worked prior to switching to live mode, can you please confirm you have added a live api key in the settings page? The error is likely to be a knock-on effect from another issue – were there any other php warnings or errors in the log immediately prior to this fatal error? Thanks.
@kadament
php version 8.0.28
yes I added the live api and proceeded to do a £1 transaction which was successful.
2023-03-13T16:41:52+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T16:43:08+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T16:52:08+00:00 INFO Reached process payment without errors. Saving: CU0029JNPKVS2F PRQ00035SYC56JQ PM00QYA04SDK6R
2023-03-13T16:52:08+00:00 INFO GC payment was successful but payment is still pending at checkout completion -> order: 9442
2023-03-13T16:52:21+00:00 INFO Webhook payment event, order: 9442 payment status is updated but order status stays the same. PaymentID = PM00QYA04SDK6R webhookID = EV03FDR5Q63G7E
2023-03-13T16:52:21+00:00 INFO Webhook payment event, order: 9442 payment status is updated but order status stays the same. PaymentID = PM00QYA04SDK6R webhookID = EV03FDR7DPAF3V
2023-03-13T16:54:04+00:00 INFO Webhook payment event, order: 9442 status updated to: processing paymentID = PM00QYA04SDK6R webhookID = EV03FDR9VR7TJW
2023-03-13T16:55:04+00:00 INFO Webhook payment event, order: 9442 status updated to: processing paymentID = PM00QYA04SDK6R webhookID = EV03FDR9VR7TJW
2023-03-13T17:08:48+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:09:08+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:10:01+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:11:39+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:13:05+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:14:11+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:19:27+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:21:12+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T17:22:19+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
2023-03-13T18:50:05+00:00 ERROR Webhook payment event recieved, but no order exists with Payment ID: PM00QYB0M8CEE7
2023-03-13T19:38:55+00:00 ERROR Error recieving customer ID | payment ref | payment ID from GC
Then these-
2023-03-13T13:32:26+00:00 CRITICAL Allowed memory size of 268435456 bytes exhausted (tried to allocate 14684160 bytes) in /homepages/37/d4295971963/htdocs/wordpress/wp-content/plugins/wordfence/lib/wfConfig.php on line 711
The next error prior was 2 days before this issue.
many thanks for your dedication and help by the way.
Hi many thanks for this, the issue with the plugin is definitely due to the PHP version. WordPress core is still in beta for PHP versions above 7.4, and as a result unfortunately we can’t guarantee the plugin works with PHP 8 yet. Apologies for this as this isn’t that clear on the plugin page. I’ll try to get it tested and working with PHP 8 as soon as possible, and will notify you. It’s worth also noting that one of the other errors included in your logs shows Wordfence running out of memory. This is what will have caused your server to crash. Thanks for notifying us of the issue, and we will come back to you as soon as we can guarantee it works with PHP 8. If it’s possible, are you able to please amend your initial review to reflect our updated understanding of the issue? Mainly so we don’t scare other potential users about data losses? Thanks.
Sure I have edited the review. Hope you’re happy with the update.
Slightly disappointed my host have not picked up on the error you pointed out.
As you can tell I am a complete novice.
I look forward to hearing from you about the testing and after how you have dealt with this I will be trying the plugin again once you e got back to be about version 8.
Many thanks, I hope you manage to resolve your other memory issues, and we will let you know re php 8 as soon as we can. 🙂
