Beauty of Code (woo-hc)

Hey @mike2mike ,

It’s worth noting that due to how WP Cron works, it’s not uncommon to have a few past-due actions, as tasks sometimes miss their scheduled dates.

However, if you notice multiple past-due actions that are more than a day old, this could signal a potential issue with WP Cron on your site. When WP Cron isn’t functioning properly, it may affect tasks such as database updates and other background processes.

To help resolve this, could you please navigate to WooCommerce → Status → Scheduled Actions → Pending and try running the pending actions manually?

Additionally, this support guide is helpful in debugging WP Cron:

• Debugging WP Cron

Let us know how this goes!

Hey @roadkill1 ,

The error you’re seeing (Uncaught TypeError: hash_equals(): Argument #2 ($user_string) must be of type string, null given) suggests that WooCommerce is attempting to verify data (possibly a security token) but is encountering a null value instead of a string.

This is often related to an issue with session handling or the data being passed to WooCommerce after a redirect. Can you check if clearing your site cache makes any difference.

If that makes no difference, can you head over to WooCommerce → Status → Tools and do the following:

• WooCommerce transients – Clear transients
• Expired transients – Clear transients
• Product lookup tables – Regenerate

Next, please clear all browser cache and see if that does the trick. If the issue is still present, please try temporarily disabling any caching and security plugins since they can also cause unexpected issues like this.

Please let us know how this goes!

Hey @gwenm ,

Just wanted to add that we have our developer resources portal that can help you get going, feel free to check it further if you need more help with this:

https://developer.woocommerce.com/

Another option is to check our customizations page to hire an expert who can help you with a custom solution: 

• WooExperts
• Codeable.io

Additionally, you can reach out in one of the channels below with customization questions:

• WooCommerce Advanced Facebook Group
• WooCommerce Developer Slack Channel

Hope this helps!

Hey @gavinbrunton ,

Thanks for creating a new topic in the WooPayments support forum!

If I’m not mistaken, Google Pay and Apple Pay typically rely on the address information selected within these wallet applications to calculate shipping options and costs on the site.

When Google Pay or Apple Pay is selected, the addresses stored within these wallets are passed to WooCommerce, which then uses this address to determine applicable shipping methods and rates for the order​​.

Since further support for this will be provided in the WooPayments forum, I’m going to mark this topic as resolved, however feel free to create a new topic if you need any further help with WooCommerce core.

Hope this helps!

Hey @mcdeth ,

Glad to hear that this has been sorted! I’ll go ahead and mark this as resolved then, however feel free to create a new topic if you need any further help. 😀

Cheers!

Hey @aaaamans ,

Thanks for reaching out! Do you recall any updates/changes made to the site or server before this issue first popped up?

Since you’ve mentioned this only happens with specific products, are there any similarities with the products that experience this issue (i.e, simple products, variable products, subscription products.)

Additionally, can you please share a copy of the following, hopefully it will give us some insight into what’s going on here:

• System Status Report: navigate to WooCommerce → Status. Select Get system report and then Copy for support.
• Fatal Error log: Share a copy of any fatal error log found under WooCommerce → Status → Logs.

Cheers!

Hey @ole_wilkenburg ,

I’m sorry to hear about the issue you’re experiencing when activating WooCommerce! Just to confirm, are all the WooCommerce Server Recommendations and WordPress requirements met at the moment for the site experiencing the issue?

If so, it’s possible that there may be a theme/plugin conflict causing the issue. To check, you’ll need to deactivate all plugins and switch to a default theme.

Are you able to access your WordPress admin area? If not, please try logging into your site via cPanel or FTP and renaming the plugins folder under /wp-content/plugins/ to something like plugins.old. This will deactivate all plugins on the site.

Then, try accessing your WP admin again. Once logged in, please switch to a default theme, such as Storefront, activate WooCommerce, and see if this resolves the issue.

If so, you can reactivate each plugin one by one until you identify the one causing the error.

Please let us know how this goes!