Woocommerce connection with Lightspeed

I can see how disruptive this is, especially when the WooCommerce admin page at /wp-admin/admin.php?page=wc-admin is not loading and instead showing the generic “Oops, something went wrong” message. Let’s work through this methodically and get you back in.

From your System Status Report, a few things stand out:

• WooCommerce 10.5.1
• PHP 8.2.30 on LiteSpeed
• HPOS enabled
• Daily Cron not scheduled
• XStore child theme with multiple WooCommerce template overrides

The wc-admin screen relies heavily on JavaScript and scheduled actions, so this type of error is often caused by one of the following: a plugin conflict, a theme override issue, a caching or optimization layer, or a blocked REST request.

Here are the next steps I recommend:

Clear all caches, including server cache and any LiteSpeed caching layers.
Go to WooCommerce → Status → Tools and clear expired transients, WooCommerce transients, product lookup tables, and template cache.
Temporarily switch to a default theme such as Twenty Twenty-Four and test again.
Temporarily deactivate all plugins except WooCommerce, then reactivate them one by one while testing the wc-admin page each time.
Open your browser console while loading the page and check for any JavaScript errors.

Since HPOS is enabled, you can also temporarily disable it under WooCommerce → Settings → Advanced → Features and test again, just to rule out any datastore conflicts.

Additionally, I noticed that Daily Cron is not scheduled. WooCommerce depends on scheduled actions for wc-admin data syncing. You can review how WP Cron works here: https://developer.ww.wp.xz.cn/plugins/cron/understanding-wp-cron-scheduling/

And WooCommerce scheduled actions here: https://woocommerce.com/document/understanding-the-woocommerce-system-status-report/scheduled-actions/.

If the issue persists after the conflict test, please enable debugging by adding the following to your wp-config.php:
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );

Then reproduce the issue and share the generated debug.log via https://pastebin.com or https://gist.github.com rather than pasting it directly into the forum.

Let’s start with the plugin and theme conflict test and take it from there. I’m here and ready to continue troubleshooting with you.

Thread Starter

(@sunemorton)

THank you, I did the first two steps but now the website is completely off?

LovingBro (woo-hc)

(@lovingbro)

Thank you for the update. When you mentioned that the website is completely off, could you please clarify what you are seeing on your end? Is it a blank white screen, a fatal error message, a 500 error, or something else entirely?

I have checked your site at https://www.golfboutique.co.za and it appears to be loading correctly from here, as shown in this screenshot: https://cln.sh/SQTcSS7bh9xL2fTHwygh.

To better understand what is happening on your side, could you please share a short screen recording using https://www.loom.com showing exactly what you see when you try to access the site and the WooCommerce admin page? That will help us pinpoint whether this is a local caching issue, a permissions issue, or something server side.

Once we see what you are seeing, we can guide you precisely on the next step.

Thread Starter

(@sunemorton)

The website is off and on the whole time. would you be able to login and assist?

Plugin Support

Frank Remmy (woo-hc)

(@frankremmy)

That sounds really frustrating.

We’re not able to log in to your site due to the forum guidelines, but we can still narrow this down together.

Since you’re seeing the site go off and on, this usually points to either:

Server/resource issues (CPU, memory, or limits being hit intermittently), or
A fatal error being triggered only under certain conditions (specific pages, plugins, or traffic).

A few focused next steps:

Check with your host for uptime and errors. Ask them to check:
If the site is hitting any resource limits (CPU, RAM, I/O) or if there are any recent PHP error or 500 logs.
Check WooCommerce → Settings → Logs for any related entries and share via pastebin.com

That should point us to the root cause. Looking forward to your response.

Thread Starter

(@sunemorton)

Thank you, our server provider have checked a few times but the problem is not on their side.

THere is a few logs over the last period which ones do I need to send?

LovingBro (woo-hc)

(@lovingbro)

Thank you for the update and for checking with your server provider again. I can see there are several logs available, and reviewing the correct one will definitely help us narrow this down properly.

Please share the relevant log via https://pastebin.com or https://gist.github.com instead of pasting it directly into the thread. This helps keep the forum clean and readable, and makes it easier for everyone to review the details.

Before sharing, feel free to quickly review the log and redact any sensitive information such as email addresses, API keys, or site paths.

For this issue, please share:

• The most recent fatal error or PHP error log from the time the site goes offline
• Any WooCommerce log entries around the same timestamp under WooCommerce → Settings → Logs
• If available, the server error log for the same timeframe

Once you share the pastebin links, we will go through it carefully and guide you on the next step.

Thread Starter

(@sunemorton)

THank you but the size of the logs is to big to past on pastebin. Limit is 417 and the log files is 5mb

Plugin Support

Frank Remmy (woo-hc)

(@frankremmy)