Guy Chapman

Hey there @oliverrealize, despite this being marked as resolved and the github request being created, the underlying resource demands of WooCommerce were never resolved. As noted throughout this thread, I just threw more resources at my site, turned off everything I could and moved to less resource hungry components wherever I could.

Good luck!

Thanks @thup90, appreciate you logging that. I’ve got a working solution now so all good from this end but it will be good to see if there are any optimisations that come from that GGH issue.

Cheers,
Guy

Thanks @seanomattic,

I’d be interested in what the Dev team have to say. Even if it’s that these Apache settings always have to be adjusted like this it would be good to know. I searched for a WooCommerce page for any detailed recommendations on this but couldn’t find anything, may have missed it, but it would be great to see a definitive page on recommended settings – even if they are just a minimum starting point.

Cheers
Guy

Hi @seanomattic,

Thanks for your comments. Yes, I tested it on vanilla, staging and production instances on the host and all displayed the error – even the absolutely minimal vanilla installation. Testing on a local dev did not have the issue.

I went back to my hosting company and asked them to have a further look as I couldn’t see anything in any logs. I also gave them access to WP/WC admin so they could reproduce the error using the WooCommerce Home and Analytics pages. Following that they made the configuration changes listed below to Apache and this seems to have resolved the issue.

According to them, the Analytics page is considerably heavy and makes 230+ requests and increases the load of the VPS.

The admins have increased the following VPS limits:
ServerLimit 4 => 30
FcgidMaxProcesses 1000 => 1500
FcgidSpawnScoreUpLimit 10 => 40
FcgidMaxProcessesPerClass 5 => 15

So it’s been an epic journey, I’ve optimised a ton of things in the site along the way (that needed to be done anyway so no regrets there).

It sure looks like there are some optimisation opportunities in the app but at least we found a way out the other end of this, hope all the text in here is of some use to others with similar issues.

Cheers
Guy

Hi @battouly,

Thanks so much for checking in with the dev team.

Regarding the logging, I do have pretty good access to the host and have checked server logs and have enabled php debug.

On occasions when the whole system used to freeze when opening a WooCommerce page (this is not happening now after the hosting capacity increase) there were server errors in the logs like the ones below, but that was because the whole system was dying so no surprises there. Now that loading a WooCommerce page no longer brings down the host nothing is written to the server logs when the json errors are displayed in the browser console.

mod_fcgid: can't apply process slot

[error] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function

For php logging, I have tried two methods to see if anything is written out about the browser console json errors. One is to enable php logging via the php.ini that I have access to modify via the host, the other by disabling that (as they conflict) and using this in wp-config.php

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

Neither method writes out any log files when repeatedly loading the WooComerce pages with the errors.

Also, nothing new is reported at WooCommerce > Status > Logs

I agree, you would think the 503 error reported in the browser console would also be in the server log, but there is nothing there. If there are any other tricks to getting logging happening I’m happy to give them a go.

I’ve had a couple of tickets open with the hosting company where they have checked logs and have raised limits on the host but report that nothing looks out of place for them.

I mentioned the Elementor slowness previously as it was vastly worse as soon as WooCommerce plugin is enabled. Perhaps this is just because Elementor is bloated / heavy and shows up the issue easily. The console errors displayed are with WooCommerce json/ajax/rest links.

Database issues could be worth exploring further. The error is repeatable on a test vanilla install of WP with a new db. Any tips on where to look for logging there are more than welcome.

Cheers,
Guy

Clearly this has stalled with no solution apparent so just for the record, these are some examples of the failed links that show up in the browser console (as also shown in the images attached throughout this ticket that may disappear over time). The domain in the path is replaced with ‘~’

Home
~/wp-json/wc/v3/products?status=publish&_fields%5B0%5D=id&page=1&per_page=1&_locale=user
~/wp-json/wc-admin/onboarding/profile?_locale=user

~/wp-json/wc-analytics/admin/notes?page=1&per_page=5&status=unactioned&type%5B0%5D=info&type%5B1%5D=marketing&type%5B2%5D=survey&type%5B3%5D=warning&
orderby=date&order=desc&_fields%5B0%5D=id&_fields%5B1%5D=name&_fields%5B2%5D=title&_fields%5B3%5D=content&_fields%5B4%5D=type&_fields%5B5%5D=status&_fields%5B6%5D=actions&
_fields%5B7%5D=date_created&_fields%5B8%5D=date_created_gmt&_fields%5B9%5D=layout&_fields%5B10%5D=image&_fields%5B11%5D=is_deleted&_fields%5B12%5D=is_read&_fields%5B13%5D=locale&_locale=user

~/wp-json/wc-analytics/reports/performance-indicators?after=2023-10-06T00%3A00%3A00&before=2023-10-06T09%3A07%3A55&stats=revenue%2Ftotal_sales%2Corders%2Forders_count&_locale=user

Customers
~/wp-json/wc-analytics/products/low-in-stock?page=1&per_page=1&low_in_stock=true&status=publish&_fields%5B0%5D=id&_locale=user
~/wp-json/wc-admin/options?options=woocommerce_ces_tracks_queue&_locale=user
~/wp-json/wc-admin/options?options=woocommerce_admin_transient_notices_queue%2Cwoocommerce_admin_install_timestamp&_locale=user
~/wp-json/wc-analytics/admin/notes?page=1&per_page=25&type=error%2Cupdate&status=unactioned&_locale=user
~/wp-json/wc-analytics/data/countries?_locale=user
~/wp-json/wc-analytics/reports/customers?orderby=date_last_active&order=desc&page=1&per_page=25&_locale=user
~/wp-json/wc-analytics/reports/customers/stats?fields%5B0%5D=customers_count&fields%5B1%5D=avg_orders_count&fields%5B2%5D=avg_total_spend&fields%5B3%5D=avg_avg_order_value&_locale=user

Analytics
~/wp-json/wc-admin/plugins/installed?_locale=user
~/wp-json/wc-admin/options?options=woocommerce_ces_tracks_queue&_locale=user
~/wp-json/wc-admin/options?options=woocommerce_admin_transient_notices_queue%2Cwoocommerce_admin_install_timestamp&_locale=user
~/wp-json/wc-analytics/admin/notes?page=1&per_page=25&type=error%2Cupdate&status=unactioned&_locale=user
~/wp-json/wc-analytics/reports/performance-indicators?after=2022-10-01T00%3A00%3A00&before=2022-10-06T23%3A59%3A59&stats=revenue%2Ftotal_sales%2Crevenue%2Fnet_revenue%2Corders%2Forders_count%2Cproducts%2Fitems_sold%2Cvariations%2Fitems_sold&_locale=user
~/wp-json/wc-analytics/reports/performance-indicators?after=2023-10-01T00%3A00%3A00&before=2023-10-06T09%3A26%3A37&stats=revenue%2Ftotal_sales%2Crevenue%2Fnet_revenue%2Corders%2Forders_count%2Cproducts%2Fitems_sold%2Cvariations%2Fitems_sold&_locale=user
~/wp-json/wc-analytics/reports/revenue/stats?order=asc&interval=day&per_page=100&after=2023-10-01T00%3A00%3A00&before=2023-10-06T23%3A59%3A59&fields%5B0%5D=total_sales&fields%5B1%5D=net_revenue&fields%5B2%5D=refunds&fields%5B3%5D=shipping&_locale=user
~/wp-json/wc-analytics/reports/revenue/stats?order=asc&interval=day&per_page=100&after=2022-10-01T00%3A00%3A00&before=2022-10-06T23%3A59%3A59&fields%5B0%5D=total_sales&fields%5B1%5D=net_revenue&fields%5B2%5D=refunds&fields%5B3%5D=shipping&_locale=user
~/wp-json/wc-analytics/reports/orders/stats?order=asc&interval=day&per_page=100&after=2023-10-01T00%3A00%3A00&before=2023-10-06T23%3A59%3A59&fields%5B0%5D=orders_count&fields%5B1%5D=avg_order_value&_locale=user
~/wp-json/wc-analytics/reports/performance-indicators?after=2023-10-01T00%3A00%3A00&before=2023-10-06T23%3A59%3A59&stats=revenue%2Ftotal_sales%2Crevenue%2Fnet_revenue%2Corders%2Forders_count%2Cproducts%2Fitems_sold%2Cvariations%2Fitems_sold&_locale=user
~/wp-json/wc-analytics/reports/orders/stats?order=asc&interval=day&per_page=100&after=2022-10-01T00%3A00%3A00&before=2022-10-06T23%3A59%3A59&fields%5B0%5D=orders_count&fields%5B1%5D=avg_order_value&_locale=user
~/wp-json/wc-analytics/leaderboards?after=2023-10-01T00%3A00%3A00&before=2023-10-06T23%3A59%3A59&per_page=5&persisted_query=%7B%7D&_locale=user

• This reply was modified 1 year, 1 month ago by Guy Chapman.

Thanks for that @battouly,

Just to add some additional info, in the vanilla install, with just WC plugin and upgraded infra, when repeatedly reloading the WC Home page each time errors come up in the browser console, just occasionally, perhaps 1 in 15 times, the page will load correctly with no errors (the errors are usually from the items in the In box). So it’s not a permanent blockage somewhere that never works, hopefully there is someone who understands the WooC interactions end to end who can chime in on this.

Cheers

• This reply was modified 1 year, 2 months ago by Guy Chapman.

In the hosted test environment that is vanilla WP with only WC plugin installed, I updated WC to 8.1.0 that was just released and I get the same errors plus this new one (that doesn’t appear on every page load)…

Error: Minified React error #130; visit https://reactjs.org/docs/error-decoder.html?invariant=130&args[]=undefined&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Good to see someone has spent time changing the big purple exclamation mark error icon to a small grey one. This is good, makes it easier to fit all the errors onto one tidy screen-shot now ??

https://snipboard.io/OXPYos.jpg

https://snipboard.io/czkiSf.jpg

• This reply was modified 1 year, 2 months ago by Guy Chapman.
• This reply was modified 1 year, 2 months ago by Guy Chapman.

Hi @wpnomad,

In the comments somewhere above I mentioned that I set up a local instance that at first had the errors but is fine now but local and useless.

I don’t have another host to try a vanilla setup on but I’ve checked in a couple of times with the hosting team and they don’t see anything specific.

So, what I have done since my last comment, in attempts to reduce load anywhere I can is…

1. I have ditched the Qode Bridge Theme I was using as it was quite heavy with third-party plugins and replaced it with Kadence that is know to be more lightweight. A bit of rapid reworking of the site and have that in place. It’s more of an impact for the front end of course. It may have made things a bit more responsive but didn’t fix the admin slow pages or the WooCommerce console errors.
2. So next I’ve upgraded hosting infra, again, Initially I went from shared hosting to a single CPU VPS and have just updated again to 2 CPU and double the RAM and storage available. This has made everything a lot snappier in front and back end and I’m able to at least get Elementor pages to open for editing without freezing. I’m also able to open WooCommerce admin pages without it taking down the whole site while all the console errors time out… so some progress

Certainly seems there is a hosting capacity component to some of this that may be out of the picture now but there are still a rash of errors on Woo pages that take time fail, then show up in the console. There is a jump in memory use when this happens, less of an issue now but on the previous VPS, as soon as I clicked on a Woo page, memory use would jump from say 20% up tp 60% and hang everything for a few minutes, perhaps until something in json / rest or elsewhere, timed out, and the errors show up in the browser console.

so current state is that I have a useable site, with lots of Woo console errors, and Elementor page edit times of about 30 seconds.

From the cast of thousands who have dipped into this ticket, it sure would be good to talk to someone who understands the WC Ajax / rest / json stuff, how it hangs together and authenticates, what is calling what, where the timeouts may be…

Cheers,
Guy

• This reply was modified 1 year, 2 months ago by Guy Chapman.
• This reply was modified 1 year, 2 months ago by Guy Chapman.

Hi Sean,

Thanks for the reply. Yes, I’ve never seen that welcome page work, ever. In perhaps 10 installations over time on this site. I’ve always had to use the skip link in the top right. Although today I went to the link to it in > Settings > Help > Set up wizard, and did manage to get it to work that way.

Everything from my last post is from the hosted site where I did the clean install.

In the local instance, when I first set it up I got the same errors but not since. Just this one error on the local instance ~.local/wp-json/jetpack/v4/connection/data?_locale=user

Locally, page load time to open a page for editing is about 6 seconds, the local instance has the same setup as production with the Bridge Theme, Elementor and the suite of plugins. As expected.

The fresh hosted Test instance is also fast to open a page for editing as it has none of the heavy theme and page builder stuff. Opening WooCommerce Home page is slow though. The blank page loads then it takes about 60 seconds for those console errors to come up. Once they appear some parts of the page render. Usually not the inbox, but it did fully render just now… so inconsistent

Cheers,
Guy

edit to say just reloaded the WooCommerce page again on the hosted test site and got the full suite of console errors again :-{

• This reply was modified 1 year, 2 months ago by Guy Chapman.

Hi @seanomattic,

I took the conflict testing idea to the extreme and created a clean install of WP 6.3.1 with a fresh database on my VPS host (same as production but no load coming from prod currently). I left the default theme Twenty Twenty-Three as is. Set Australian location and time. Deleted the preinstalled plugins ‘Hello Dolly’ (wtf?) and Akismet.

Did some clicking around and can see no errors via the browser console. All good so far.

Installed WooCommerce and immediately on the Welcome to Woo! page (which always fails on any installation) got a couple of errors. https://snipboard.io/BJsKkm.jpg Deselect data sharing and click ‘Skip guided setup’ as this is the only way to progress, select country. Hence the Onboarding: skipped status in the system report below.

Clicked on the WooCommerce menu item in the Left Nav. Immediately get errors in the browser console. https://snipboard.io/JRXZbH.jpg

Disabling WC Analytics seems to reduce the number of errors but not fully

Analytics on https://snipboard.io/BhrSZO.jpg

Analytics off https://snipboard.io/XC3BSz.jpg

`
### WordPress Environment ###

WordPress address (URL): https://tst.guychapman.net/wp
Site address (URL): https://tst.guychapman.net
WC Version: 8.0.3
REST API Version: ? 8.0.3
WC Blocks Version: ? 10.6.6
Action Scheduler Version: ? 3.6.1
Log Directory Writable: ?
WP Version: 6.3.1
WP Multisite: –
WP Memory Limit: 1 GB
WP Debug Mode: –
WP Cron: ?
Language: en_AU
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 8.0.28
PHP Post Max Size: 512 MB
PHP Time Limit: 300
PHP Max Input Vars: 5000
cURL Version: 7.61.1
OpenSSL/1.1.1k

SUHOSIN Installed: –
MySQL Version: 8.0.30
Max Upload Size: 256 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### Database ###

WC Database Version: 8.0.3
WC Database Prefix: wp_
Total Database Size: 4.26MB
Database Data Size: 2.60MB
Database Index Size: 1.66MB
wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_actions: Data: 0.02MB + Index: 0.11MB + Engine InnoDB
wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_actionscheduler_logs: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_comments: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_options: Data: 1.52MB + Index: 0.03MB + Engine InnoDB
wp_postmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_posts: Data: 0.05MB + Index: 0.06MB + Engine InnoDB
wp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wc_admin_note_actions: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
wp_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB
wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB
wp_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
wp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_product_meta_lookup: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB

### Post Type Counts ###

attachment: 1
page: 7
post: 2
wp_global_styles: 1
wp_navigation: 1
wp_template: 2

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?

### Active Plugins (1) ###

WooCommerce: by Automattic – 8.0.3

### Inactive Plugins (0) ###


### Settings ###

API Enabled: –
Force SSL: –
Currency: USD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: –
Enforce Approved Product Download Directories: ?
HPOS feature screen enabled: –
HPOS feature enabled: –
Order datastore: WC_Order_Data_Store_CPT
HPOS data sync enabled: –

### WC Pages ###

Shop base: #7 - /shop/
Cart: #8 - /cart/
Checkout: #9 - /checkout/
My account: #10 - /my-account/
Terms and conditions: ? Page not set

### Theme ###

Name: Twenty Twenty-Three
Version: 1.2
Author URL: https://www.ads-software.com
Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build
personally we recommend using a child theme. See: How to create a child theme

WooCommerce Support: ?

### Templates ###

Overrides: –

### Admin ###

Enabled Features: activity-panels
analytics
product-block-editor
coupons
core-profiler
customer-effort-score-tracks
import-products-task
experimental-fashion-sample-products
shipping-smart-defaults
shipping-setting-tour
homescreen
marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page

Disabled Features: minified-js
new-product-management-experience
product-variation-management
settings
async-product-editor-category-field

Daily Cron: ? Next scheduled: 2023-09-10 04:40:33 +10:00
Options: ?
Notes: 59
Onboarding: skipped

### Action Scheduler ###

Complete: 3
Oldest: 2023-09-09 04:41:45 +0000
Newest: 2023-09-09 04:45:41 +0000

Pending: 1
Oldest: 2023-09-10 04:41:45 +0000
Newest: 2023-09-10 04:41:45 +0000


### Status report information ###

Generated at: 2023-09-09 15:32:26 +10:00
`

Hi @simplysaru,

Apologies, I was unclear in that last comment, the Mini Cart warnings are indeed all in the front end, not admin. It was just an observation about another Woo-related component that seemed to be generating junk. More of a rant than a root cause for this issue.

In the Admin area, when loading the WooCommerce home page, after initially getting the same console errors as production in local, they have now gone, which is good right, but I’m not sure why.

These are the only two items showing, one a warning, the other some jetpack remnant.

[Warning] position prop in wp.components.Dropdown is deprecated since version 6.2. Please use popoverProps.placement prop instead. Note: Note that the position prop will override any values passed through the popoverProps.placement prop. (deprecated.min.js, line 2)

[Error] Failed to load resource: the server responded with a status of 403 () (data, line 0)
https://guychapman-prd-local2.local/wp-json/jetpack/v4/connection/data?_locale=user

I have been doing everything I can to make the local instance as close to the production one, not all settings are possible to get identical but it’s close. I had been making sure the php settings in local matched production but putting them back to vanilla on local didn’t cause the errors to return.

Those two errors appear with all plugins enabled or with only WooCommerce enabled.

Cheers,
Guy

• This reply was modified 1 year, 2 months ago by Guy Chapman.

Just a side note, while reviewing those console errors, I noticed these 30 or so warning coming up on every page…

https://snipboard.io/hSiYs9.jpg

Turns out they are generated by the WooCommerce Mini Cart Widget that was in the header. Removing that stopped those errors (I’ve replaced it with the plugin WP Menu Cart for now).

I’ve also added the plugin Disable Cart Fragments as well in an attempt to reduce the impact of WooCommerce on every page load.

Incremental improvement but not fixing the initial issues yet.

Hi?@simplysaru,

Ignore that previous comment, I tried to edit it but just missed the window. I’ve got a better replica of production running locally now via Local and the WooCommerce errors are all still visible (my previous attempt wasn’t configured correctly).

Cheers
Guy

Hi @simplysaru,

Thanks for picking this up.

I’ve got some local instances running, of sorts, using Local. It’s a bit complex to get a good replica of prod running locally so I started with a vanilla local, added WooCommerce and have no json errors in the console there when loading Woo pages (other than a jetpack connection error and the usual warning that Woo is loading a lot of unused css cruft).

Then I moved on to getting copy of my hosted test site running locally that has the the Theme, Elementor and Woo… all good there too, no errors.

Next a bit of a hack job to get a production copy sort of working locally, but well enough to load Admin pages and see there are no errors when loading Woo pages

I could burn a bunch more time getting these working better and looking more like the live version but perhaps this is enough to get you the info you are after?

Cheers,
Guy