fongmh

Hi OP, thanks for your reply.

I did as you suggested and created a staging site. The errors were replicated so I started messing around with the staging site only to discover that adding a new shipping method seemed to have resolved the issue. Inspecting the page on chrome checkout also showed that there were no longer any javascript issues. I did the same on my main page, and voila, problem resolved.

At this point, I’m still not sure what caused the error in the first place but it seems that the fix is to add a new shipping method which, presumably, repopulates the database with some vital information. I don’t have the knowledge or patience to try and understand it any more than that, I’m afraid.

But thank you for your suggestions as creating the staging site was a good idea to let me just try crazy things until something worked!

Hi,

I changed the remote backup option to Google Drive and the backup succeeds. I think this suggests that there may be an issue with the Dropbox script. As I really have no preference whether it backs up to Google or Dropbox, I will consider this matter as resolved on my end.

Thanks for your help.

Hi, I’ve tried your suggestions but it throws up the same error. Log file here:

https://drive.google.com/file/d/16pj7q_6SKq9OCNQaF4wpZ10sp7Ud7eJ5/view?usp=sharing

Cheers,
MH

Sure.

https://drive.google.com/file/d/1j5HCzbjhJ0A3M_9Cwh-e2_AyZn6WMcmc/view?usp=drive_link

I’ve checked the other events and done keyword searches on both the product names and SKU, but the two transactions were not logged anywhere. If this helps, searching the product name and/or SKU yields the two entries in my original post.

Hi @kokomoweb,

Thanks for the quick reply. I’ve tried both your suggestions but it doesn’t seem to have sped up loading time. I’m wondering if it could be related to the sheer number of transactions and users that I have on my site.

You are also right in saying that I am currently on a shared server. I may try your plugin again once we’ve migrated to a dedicated box because I thought your plugin was extremely useful.

Thanks again for the quick reply.

Cheers,
MH

Updating to version 1.3.1 seems to have fixed the issue.

Hi @robert681

We updated WooCommerce to version 5.1 and everything works as expected. Hope this helps others facing the same problem.

Hi @robert681

Yes, I am running WooCommerce 4.8.0 as well. As with @becarlos I cannot update to WooCommerce 5.0 for the time being. Will try to do so this weekend and update.

Thanks!

Hi, I have reproduced the error on my site as well. Similar to @simonbbs, our users encounter the same issue when they click the ‘Lost Password’ link and throws up the following error:

Fatal error: Uncaught ArgumentCount

Error: Too few arguments to function WSAL_Sensors_LogInOut::event_user_requested_pw_reset(), 1 passed in /home2/litbooks/public_html/wp-includes/class-wp-hook.php on line 287 and exactly 2 expected in /home2/litbooks/public_html/wp-content/plugins/wp-security-audit-log-premium/classes/Sensors/LogInOut.php:540

Deactivating WP Activity Log solved the issue. I haven’t had the time yet to do a plugin-by-plugin check but will try to do so when I can.

FMH