linsisterherb

Ok nevermind, it’s fixed. It started working when I just pressed “publish”. I guess I was only viewing the preview as a draft. The thing is that it used to show up on my website and then stopped appearing.
Thanks anyways for your time and help.

• This reply was modified 3 months, 1 week ago by linsisterherb.

I’ve followed your recommendations, and still no luck unfortunately. I have not disabled any scripts nor have i added any custom script into the theme’s function.

Howdy,

My host is still attempting to resolve this issue with the database.

mysqli_real_connect(): (HY000/2059): Authentication plugin 'sha256_password' cannot be loaded: /usr/lib64/mysql/plugin/sha256_password.so: cannot open shared object file: No such file or directory

They say that they’re just finishing up, but unfortunately the issue with the past-due actions persists. I’ll write an update here when they hopefully fix it.

In the meantime, I’m trying to set us SSH in order to use the WP CLI command.

Thanks for your reply Roxy S.

I figured that the Woocommerce database was unable to update due to the issues with my Action Scheduler. I think this because the whole time I’ve had this issue, I have the notification that WooCommerce database is updating in the background. When I click the “You can manually run queued updates here” button, it leads me the Action Scheduler, where the only action I’m offered is “delete”. Also, the only action it’s been attempting is for the hook action_scheduler/migration and the group action-scheduler-migration, which I don’t think have to do directly with updating the WC database.

Now, after replacing WP Cron with a real cron job, as suggested above (according to these instructions https://community.hostek.com/t/wordpress-configuring-a-manual-wp-cron-job/263) the issue persists, but the notification says that my disabled WP Cron may prevent the update from completing. Therefore, I do not think it’s really an issue with WP Cron interfering with the update.

I have been looking into solving the issue according to this guide https://clicknathan.com/web-design/woocommerce-actionscheduler-table-error/

though this isn’t your domain, I’m just writing this part for yours or anyone else’s information. I ran into an error in myPHP when I attempted to set the tables to “index” or “primary” according to the guide above. My host support suggested I delete and then reinstall Woocommerce to fix the corrupt tables, which of course I’ve already tried and it didn’t fix the issue.

I have followed all of your suggestions

• disable server and website cache
• deactivate all plug-ins other than WooCommerce
• Change theme to storefront
• replace WP Cron with a real Cron job (according to this tutorial https://community.hostek.com/t/wordpress-configuring-a-manual-wp-cron-job/263)
  
  but the issue persists. Like I said earlier, I am unable to delete the ActionScheduler folder without crashing the admin page of my website (interestingly, the main domain linsisterherb.com does not crash when I do this).
  
  When I re-upload the ActionScheduler after deleting it, the cycle restarts of the action being created, started, and ignored several times a minute

2023-10-17T14:15:32+00:00 CRITICAL Uncaught RuntimeException: Error saving action: Database error. in C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php:118
Stack trace:
#0 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php(62): ActionScheduler_DBStore->save_action_to_db()
#1 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\ActionScheduler_ActionFactory.php(244): ActionScheduler_DBStore->save_action()
#2 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\ActionScheduler_ActionFactory.php(114): ActionScheduler_ActionFactory->store()
#3 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\functions.php(81): ActionScheduler_ActionFactory->single_unique()
#4 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce-payments\vendor\woo in C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php on line 118

2023-10-17T18:43:20+00:00 CRITICAL Uncaught RuntimeException: Error saving action: Database error. in C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php:118
Stack trace:
#0 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php(62): ActionScheduler_DBStore->save_action_to_db()
#1 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\ActionScheduler_ActionFactory.php(244): ActionScheduler_DBStore->save_action()
#2 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\ActionScheduler_ActionFactory.php(114): ActionScheduler_ActionFactory->store()
#3 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\functions.php(81): ActionScheduler_ActionFactory->single_unique()
#4 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce-payments\vendor\woo in C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php on line 118

I have followed the steps you mentioned. To disable cache, I added “define(‘WP_CACHE’,true);” to my wp-config.php file. I am not quite sure how to disable my server’s cache though. Is that the something I need to speak with my host about?

After deleting the ActionScheduler library, my website crashed, so I opened it in recovery mode. I get the following message below on my plugin page

When, I reactivate WooCommerce, my issue persists, and eventually my site will crash again.

 This plugin failed to load properly and is paused during recovery mode.

An error of type E_ERROR was caused in line 1040 of the file C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php. Error message: Uncaught RuntimeException: Unable to release actions from claim id 0. in C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_DBStore.php:1040 Stack trace: #0 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\data-stores\ActionScheduler_HybridStore.php(406): ActionScheduler_DBStore->release_claim() #1 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\ActionScheduler_QueueRunner.php(176): ActionScheduler_HybridStore->release_claim() #2 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\ActionScheduler_QueueRunner.php(139): ActionScheduler_QueueRunner->do_batch() #3 C:\home\linsisterherb.com\wwwroot\wp-includes\class-wp-hook.php(324): ActionScheduler_QueueRunner->run() #4 C:\home\linsisterherb.com\wwwroot\wp-includes\class-wp-hook.php(348): WP_Hook->apply_filters() #5 C:\home\linsisterherb.com\wwwroot\wp-includes\plugin.php(517): WP_Hook->do_action() #6 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\packages\action-scheduler\classes\ActionScheduler_AsyncRequest_QueueRunner.php(52): do_action() #7 C:\home\linsisterherb.com\wwwroot\wp-content\plugins\woocommerce\includes\libraries\wp-async-request.php(147): ActionScheduler_AsyncRequest_QueueRunner->handle() #8 C:\home\linsisterherb.com\wwwroot\wp-includes\class-wp-hook.php(324): WP_Async_Request->maybe_handle() #9 C:\home\linsisterherb.com\wwwroot\wp-includes\class-wp-hook.php(348): WP_Hook->apply_filters() #10 C:\home\linsisterherb.com\wwwroot\wp-includes\plugin.php(517): WP_Hook->do_action() #11 C:\home\linsisterherb.com\wwwroot\wp-admin\admin-ajax.php(188): do_action() #12 {main} thrown

Hi,

Thank you so much. It works like a charm!