Listing products generates server error

Resolved

(@steveszm)

Cannot list Products,

When I click on Products I receive this message:
There has been a critical error on this website. Please check your site admin email inbox for instructions.

The other Products options pages come up fine, just listing them fails.

Related
I renamed the shopping page from shop to store in the same time frame. Checking the new store subdir it’s not as well populated as the original shop. AND when I browse a product the subdir it lists is shop, not store. No doubt it did not make the conversion as I would have hoped. Possibly there already was a store directory when I started renaming the shop page which might have wrecked the logic.

I renamed the store to store1 and copied shop into store and tried to list products but it still gives the same (above) error. Before I dig a deeper hole I decide to check on this forum. (I doubt it’s WooCommerce related but more likely my renaming.)

I reached out to the hosting company who pulled the three following warnings:

Warning: include_once(/home/growpe5/public_html/wp/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php): failed to open stream: No such file or directory in /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/includes/class-woocommerce.php on line 515

And indeed the directory action-scheduler is not there, but I do find it under
shop.growpermaculture.com/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php.

Warning: include_once(): Failed opening ‘/home/growpe5/public_html/wp/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php’ for inclusion (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’) in /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/includes/class-woocommerce.php online 515

Warning: file_get_contents(/home/growpe5/public_html/wp/wp-content/plugins/woocommerce/packages/woocommerce-blocks/woocommerce-gutenberg-products-block.php): failed to open stream: No such file or directory in /home/growpe5/public_html/wp/wp-includes/functions.php on line 6633

### WordPress Environment ###

WordPress address (URL): https://growpermaculture.com/wp
Site address (URL): https://growpermaculture.com
WC Version: 6.6.0
REST API Version: ✔ 6.6.0
WC Blocks Version: ✔ 7.6.0
Action Scheduler Version: ❌ Unable to detect the Action Scheduler package.
Log Directory Writable: ✔
WP Version: 6.0
WP Multisite: –
WP Memory Limit: 256 MB
WP Debug Mode: –
WP Cron: ✔
Language: en_US
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 7.4.29
PHP Post Max Size: 128 MB
PHP Time Limit: 90
PHP Max Input Vars: 1000
cURL Version: 7.83.1
OpenSSL/1.1.1o

SUHOSIN Installed: –
MySQL Version: 5.5.5-10.3.27-MariaDB-log
Max Upload Size: 128 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

### Database ###

WC Database Version: 6.6.0
WC Database Prefix: wput_
Total Database Size: 56.84MB
Database Data Size: 53.90MB
Database Index Size: 2.94MB
wput_woocommerce_sessions: Data: 0.39MB + Index: 0.02MB + Engine MyISAM
wput_woocommerce_api_keys: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_attribute_taxonomies: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_downloadable_product_permissions: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_order_items: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_order_itemmeta: Data: 0.03MB + Index: 0.02MB + Engine MyISAM
wput_woocommerce_tax_rates: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_tax_rate_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_shipping_zones: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_shipping_zone_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_shipping_zone_methods: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_payment_tokens: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_payment_tokenmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_woocommerce_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
GP Live: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_actionscheduler_actions: Data: 0.06MB + Index: 0.04MB + Engine MyISAM
wput_actionscheduler_claims: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_actionscheduler_groups: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_actionscheduler_logs: Data: 0.05MB + Index: 0.04MB + Engine MyISAM
wput_aiowps_debug_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_aiowps_events: Data: 0.56MB + Index: 0.08MB + Engine MyISAM
wput_aiowps_failed_logins: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_aiowps_global_meta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_aiowps_login_activity: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_aiowps_login_lockdown: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_aiowps_permanent_block: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_commentmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_comments: Data: 0.02MB + Index: 0.02MB + Engine MyISAM
wput_frm_fields: Data: 0.03MB + Index: 0.01MB + Engine MyISAM
wput_frm_forms: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_frm_items: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_frm_item_metas: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_commentmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_comments: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_donationmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_donormeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_donors: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_formmeta: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
wput_give_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_migrations: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_give_revenue: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_sequential_ordering: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_give_sessions: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_gla_budget_recommendations: Data: 0.11MB + Index: 0.12MB + Engine MyISAM
wput_gla_merchant_issues: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_gla_shipping_rates: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_gla_shipping_times: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_mailchimp_carts: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_mailchimp_jobs: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
wput_options: Data: 22.96MB + Index: 0.11MB + Engine MyISAM
wput_postmeta: Data: 20.64MB + Index: 0.56MB + Engine MyISAM
wput_posts: Data: 1.14MB + Index: 0.09MB + Engine MyISAM
wput_relevanssi: Data: 0.55MB + Index: 0.70MB + Engine MyISAM
wput_relevanssi_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_relevanssi_stopwords: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_snippets: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_termmeta: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_terms: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_term_relationships: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_term_taxonomy: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_usermeta: Data: 0.08MB + Index: 0.04MB + Engine MyISAM
wput_users: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wc_admin_notes: Data: 0.04MB + Index: 0.00MB + Engine MyISAM
wput_wc_admin_note_actions: Data: 0.02MB + Index: 0.01MB + Engine MyISAM
wput_wc_category_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wc_customer_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wc_download_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wc_order_coupon_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wc_order_product_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wc_order_stats: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wc_order_tax_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wc_product_attributes_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wc_product_download_directories: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wc_product_meta_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wc_rate_limits: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wc_reserved_stock: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wc_tax_rate_classes: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wc_webhooks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wfblockediplog: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wfblocks7: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wfconfig: Data: 2.73MB + Index: 0.02MB + Engine MyISAM
wput_wfcrawlers: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
wput_wffilechanges: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wffilemods: Data: 2.08MB + Index: 0.42MB + Engine MyISAM
wput_wfhits: Data: 0.87MB + Index: 0.15MB + Engine MyISAM
wput_wfhoover: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wfissues: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_wfknownfilelist: Data: 1.11MB + Index: 0.13MB + Engine MyISAM
wput_wflivetraffichuman: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wflocs: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
wput_wflogins: Data: 0.03MB + Index: 0.01MB + Engine MyISAM
wput_wfls_2fa_secrets: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
wput_wfls_settings: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
wput_wfnotifications: Data: 0.01MB + Index: 0.00MB + Engine MyISAM
wput_wfpendingissues: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wfreversecache: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wfsnipcache: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wfstatus: Data: 0.13MB + Index: 0.06MB + Engine MyISAM
wput_wftrafficrates: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_wpfm_backup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_yoast_indexable: Data: 0.17MB + Index: 0.08MB + Engine MyISAM
wput_yoast_indexable_hierarchy: Data: 0.01MB + Index: 0.03MB + Engine MyISAM
wput_yoast_migrations: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
wput_yoast_primary_term: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
wput_yoast_seo_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM

### Post Type Counts ###

attachment: 176
ct_template: 9
frm_form_actions: 2
frm_styles: 1
give_forms: 1
nav_menu_item: 112
oxy_user_library: 1
page: 75
post: 4
product: 20
revision: 250
shop_coupon: 8
shop_order: 35
shop_order_refund: 5
tribe_events: 16
tribe_organizer: 4
tribe_venue: 3
wp_global_styles: 1
wpcf7_contact_form: 9

### Security ###

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

### Active Plugins (26) ###

Akismet Anti-Spam: by Automattic – 4.2.4
All In One WP Security: by All In One WP Security & Firewall Team – 4.4.12
Code Snippets: by Code Snippets Pro – 3.1.1
Contact Form 7: by Takayuki Miyoshi – 5.6
Custom Post Type UI: by WebDevStudios – 1.12.1
Potent Donations for WooCommerce: by Aspen Grove Studios – 1.1.7
Duplicate Menu: by Jonathan Christopher – 0.2.2
Duplicate Page: by mndpsingh287 – 4.4.8
Open edX LMS and WordPress integrator (PRO): by eduNEXT – 2.6.1
Health Check & Troubleshooting: by The WordPress.org community – 1.4.5
ImageMagick Engine: by Orangelab – 1.7.4
Jetpack: by Automattic – 11.0
Mailchimp for WooCommerce: by Mailchimp – 2.6.2
Oxygen Gutenberg Integration: by Soflyy – 1.4
Oxygen Elements for WooCommerce: by Soflyy – 2.0
Oxygen: by Soflyy – 4.0
Relevanssi: by Mikko Saari – 4.16.0
The Events Calendar: by The Events Calendar – 5.16.1.1
UpdraftPlus - Backup/Restore: by UpdraftPlus.Com
DavidAnderson – 1.22.12

WC Custom Thank You: by Nicola Mustone – 1.2.1
Checkout Field Editor for WooCommerce: by ThemeHigh – 1.6.1
WooCommerce Google Analytics Pro: by SkyVerge – 1.11.1
WooCommerce PayPal Payments: by WooCommerce – 1.8.1
WooCommerce: by Automattic – 6.6.0
Asset CleanUp: Page Speed Booster: by Gabe Livan – 1.3.8.5
WP Super Cache: by Automattic – 1.7.9

### Inactive Plugins (1) ###

Yoast SEO: by Team Yoast – 19.1

### Dropin Plugins (1) ###

advanced-cache.php: advanced-cache.php

### Must Use Plugins (1) ###

Health Check Troubleshooting Mode: by  – 1.7.2

### Settings ###

API Enabled: –
Force SSL: –
Currency: USD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: donation (donation)
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: ✔

### WC Pages ###

Shop base: #60 - /store/
Cart: #63 - /cart/
Checkout: #65 - /cart/checkout/
My account: #67 - /cart/my-account/
Terms and conditions: ❌ Page not set

### Theme ###

Name: Twenty Twenty-One
Version: 1.6
Author URL: https://wordpress.org/
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: –

### WooCommerce PayPal Payments ###

Onboarded: ✔
Shop country code: US
WooCommerce currency supported: ✔
PayPal card processing available in country: ✔
Pay Later messaging available in country: ✔
Webhook status: –
Vault enabled: ✔
Logging enabled: ✔
Reference Transactions: –
Used PayPal Checkout plugin: –

### Admin ###

Enabled Features: activity-panels
analytics
coupons
customer-effort-score-tracks
experimental-products-task
experimental-import-products-task
experimental-fashion-sample-products
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
wc-pay-promotion
wc-pay-welcome-page
wc-pay-subscriptions-page

Disabled Features: minified-js
settings

Daily Cron: ✔ Next scheduled: 2022-06-19 00:39:04 -04:00
Options: ✔
Notes: 43
Onboarding: completed

### Status report information ###

Generated at: 2022-06-18 17:16:51 -04:00

Viewing 15 replies - 1 through 15 (of 18 total)

1 2 →

Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago

Looking through the db I found ‘shop’ in the posts and options tables, made one backup and one modified db and changed it to ‘store’ in the modified db.

I copied ‘modified’ to the live one. Things are improved but it looks like I may have missed some ‘shop’ reference. Product listing on the website now show ‘store’ but description of the items are still ‘shop’.

Need to find where the master reference is. Maybe in the directory holding the subdomain…

Mirko P.
(@rainfallnixfig)

3 years, 10 months ago

Hi @steveszm!

When I click on Products I receive this message:
There has been a critical error on this website. Please check your site admin email inbox for instructions.

I understand that when you click on the Products menu link in the WordPress dashboard no products are listed and you get a critical error on the screen.

WordPress address (URL): https://growpermaculture.com/wp
Site address (URL): https://growpermaculture.com

I also see that you have set the address of your main WordPress core files in a subdirectory (wp). Probably this has something to do with permalinks and you have to modify your .htaccess file as recommended here:

https://wordpress.org/support/article/giving-wordpress-its-own-directory/#htaccess-modification

Make sure you have a full backup in place of your site and database before making any changes. You could consider using a service like Jetpack or installing a plugin like UpdraftPlus. If something goes wrong it’s nice to know that you can restore your site to the previous state.
Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago
Looking at WC Analytics it reports the sales but the lederboards fail to bring up any stats.
Working my way through each menu item, products lists all products but it fails to correctly show single products sales showing 0 sales. However, under categories it shows the correct amounts.

Orders have correct data. As does revenue and overview.
Hmm, on overview now lederboards is working and product details. Must be cache phenomena.

However the store still goes to the old ‘shop’ when looking at individual products.
Marketing overview works as does coupons.

A site error email showed up listing this (which tend to happen when I try to access products in WP, i.e. not through my website but the admin menu.):
```
Error Details
=============
An error of type E_ERROR was caused in line 158 of the file /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/includes/queue/class-wc-action-queue.php. Error message: Uncaught Error: Call to undefined function as_get_scheduled_actions() in /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/includes/queue/class-wc-action-queue.php:158
Stack trace:
#0 /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/src/Admin/Schedulers/SchedulerTraits.php(185): WC_Action_Queue->search(Array)
#1 /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/src/Admin/Schedulers/SchedulerTraits.php(297): Automattic\WooCommerce\Internal\Admin\Schedulers\ImportScheduler::has_existing_jobs('import', Array)
#2 /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/src/Internal/Admin/Schedulers/CustomersScheduler.php(145): Automattic\WooCommerce\Internal\Admin\Schedulers\ImportScheduler::schedule_action('import', Array)
#3 /home/growpe5/public_html/wp/wp-content/plugins/woocommerce/src/Internal/Admin/Schedulers/CustomersScheduler.php(159): Automattic\WooCommerce\Internal\Admin\Schedulers\CustomersScheduler::schedule_import(1)
#4 /home/growpe5/public_html/wp/wp-includes/class-
```
Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago

Thank you Mirko, however, if I understand your reference correctly, this is not a new install but one that has been working perfectly well for a long time.

.htaccess does not refer to the shop either so nothing seem to apply. The problem showed up after I renamed the shop name to store.

Mirko P.
(@rainfallnixfig)

3 years, 10 months ago

Hi @steveszm,

Thanks for the additional details.

It would be helpful to share with us a screenshot of the error in your WordPress admin. I recommend https://snipboard.io for easily sharing screenshots – please follow the instructions on that page, then paste the URL in this thread. It works with Chrome, Firefox, Safari, and Edge browsers.

What I suggest is restoring the site and database to a point where it was all working fine. This preferably can be done on a staging environment first using the free WP Staging plugin – https://wordpress.org/plugins/wp-staging/.

Then, you can change the shop page name from shop to store without touching anything in the database (not recommended). Clear the transients in WooCommerce > Status > Tools and see if all works smoothly without errors.

Thereafter, apply the same steps to the live site but remember to save a full backup before making changes.

Let us know how it goes.

Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago

Really not needed as it is very plain.
White background. Centered top, empty but for a small box with two lines:

Line 1:
There has been a critical error on this website. Please check your site admin email inbox for instructions.
Line 2:
Learn more about troubleshooting WordPress.
Which points to: https://wordpress.org/support/article/faq-troubleshooting/

The URL has: domain.name/wp/wp-admin/edit.php?post_type=product

Plugin Support nicw.a11n
(@nicw)

3 years, 10 months ago

Hi @steveszm

The email referred to in the message There has been a critical error on this website. Please check your site admin email inbox for instructions. will contain what is known as a trace, or log, of the error. This should contain between seven and 20 lines of “frames” which we can use to debug the error.

It starts off in a similar way to the errors given to you by your hosting company at the beginning of this thread. Can you supply this information for us here?

It would help us identify the issue.

Gal Baras
(@galbaras)

3 years, 10 months ago

@steveszm This might be a partial installation. Have you tried reinstalling the plugin?

Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago

@nicw, yes it is included in an earlier post I made.

@gal, it’s been working well for a long time with full functionality. See above.
Adding how the problem appeared in the same time period as I made the change to the very area which is having the problem…

It looks like the easiest solution is to figure out how to reinstall WooCommerce with the least impact. I don’t know what’s affected or if I can just disable WC and reinstall or if it involves removing it and then installing it. How will that affect the data? So onto researching that.

Margaret S. woo-hc
(@margaretwporg)

3 years, 10 months ago

Hi @steveszm

it is included in an earlier post I made

Can you please share a link to that post where the error logs requested by @nicw have been shared? That information will be helpful for identifying the cause behind the problem.

I don’t know what’s affected or if I can just disable WC and reinstall or if it involves removing it and then installing it. How will that affect the data?

Normally, when you uninstall WooCommerce, only the plugin is deleted but your settings and other data (orders, products, etc) persist in a database. It takes an additional destructive step to delete everything. We’ve explained further in this guide: https://docs.woocommerce.com/document/installing-uninstalling-woocommerce/#uninstalling-woocommerce

Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago

Hi @margaretwporg
The post is on This page a few replies earlier… 🙂

OK, the problem as presented by WC is that it cannot find the Action Scheduler package, which is true. It is not where it expected it to be. When I searched for it I found it one level up in a directory called shop.(domain name), but I also see that it is not looking there but below the install directory. I will copy the missing tree structure, which I think is only one level, and see if that solves it.

Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago

Interestingly it does not like finding the action-scheduler under woocommerce/packages/. (Yeah it was a wild enough guess which is undone.)

In essence the way I look at this is that the change from renaming ‘shop’ to ‘store’ did not go as expected. I used WP to rename the page which is when this problem showed up. Having worked for a long time until this change I can’t imagine it is anything but that change which crashed the action-scheduler. (Which you can see in my first post with the full listing

I did not expect renaming the shop would mostly work but not being able to find its own static code is odd.

OK, I’ll remove the plugin and reinstall it and maybe it will then find everything it’s expecting of it’s own code. But before doing so I need to have all the ducks in a row to ensure it goes as smoothly (fast) as possible as it is a live site.

I have a couple of test subdomains but found it not all that easy to copy WP from one location to another with many small details requiring manual editing. Maybe it is only the plugin I used which is not that good?

@mirko suggested a staging plugin, I will try using that. (Thanks!) An immediate test could be to stage it to the staging domain which will tell me how well it works. OK, I’ll go down that path. And I can try to restore from a backup to it and then move forward again. (I’d be very happy to have a working staging environment, I hate working on live sites!)
Gal Baras
(@galbaras)

3 years, 10 months ago
@steveszm After making changes like this, you could use a plugin like Better Search Replace to straighten out any data references to the old URL.

It’s usually enough to replace in wp_posts and wp_postmeta, but if that doesn’t work, also look at the WooCommerce tables and wp_options.

And for completeness, also redirect the old URL to the new one using .htaccess or a redirection plugin.
- This reply was modified 3 years, 10 months ago by Gal Baras.
Plugin Support abwaita a11n
(@abwaita)

3 years, 10 months ago

OK, I’ll remove the plugin and reinstall it and maybe it will then find everything it’s expecting of it’s own code. But before doing so I need to have all the ducks in a row to ensure it goes as smoothly (fast) as possible as it is a live site.

Sounds good, @steveszm! This should resolve the action scheduler issue.

Let us know how it goes.

Thread Starter Steve Szmidt
(@steveszm)

3 years, 10 months ago

OK, this is how I almost got it fixed, that is I got it working in the staging setup using the staging plugin, and then ran the Search and Replace tool, thank you @mirko and @gal respectively for your suggestions!

Being that I used the free plugin I staged it to a sub dir, ran the S&R from ‘shop’ to ‘store’, case sensitive. Then I had to configure the permalinks for products and set the page for the store under WC-Products and it worked.

IMPORTANT, make sure you only select the tables with the prefix you got for the staging name! You end up with two sets of tables in the same db so blindly selecting all circumvents using staging in the first place.

There was a small issue with Jetpack seeing two sites under the same name, which I promptly ignored. Trying to improve it would only have created more work when moving it back to the live setup.

Now all that’s left is to try to use the staging tool to move it to the live location. Next post will hopefully report all is nominal.

One more note from this adventure. As an old developer from the early web days (-90’s) I learned to use relative links, for example, /store rather than an absolute link, in other words, https://domain.com/store. The purpose with a relative link is to cut out the extra step of needing to do a DNS query to locate the domain since you are already in the domain.

Under at least Unix based O/S’s DNS is configured by default to do a local lookup in what is a plain text file and only not finding it there to go out and do a DNS query. The local lookup could of course be done to a SQL server as well (and with the size of ISP’s these days could very well be normal now). The point I’m getting to is that for the staging tool if you use relative names it does not work.

It expects to see a full domain name or you will be redirected to the live site rather than the staging one if you click on a relative link. Running into that issue I realized why every tool I run into insists on using absolute links by default. In fact when I checked with my hosting service to see what They prefer the support guy had no idea what I was talking about and I did not get any kind of improvement from the tier above him. I asked a question about them but kept getting tips for me, random unrelated tips. I thanked him and hung up and have now given up in trying to be more effective with my links as it only makes staging more labor intensive.

I included oxygen-builder in the tag as that is what I now use to build entire sites. It replaces themes but is not a page builder but a hybrid that gives complete control of whatever features you want. It’s very fast and I will never use a theme again. The other reason for bringing it up is that I was not sure how tools like the staging plugin would deal with it. Now I can report that it works well at least with the Better Search and Replace plugin @gal suggested.