Woocommerce and AIO SEO critical error

Hi @bostralian

After updating all of my plugins, themes, as well as WordPress to the latest versions, I am now experiencing this error:

CRITICAL Uncaught RuntimeException: Error saving action: Unknown column ‘priority’

From what I understand, you’ve updated all your plugins, themes, and WordPress to the latest versions and now you’re facing an error. The error message you’re seeing, “CRITICAL Uncaught RuntimeException: Error saving action: Unknown column ‘priority’“, indicates a missing database column – a ?? bug we’re familiar with.

It seems like the problem arises when you update the All-in-One SEO Pack and WooCommerce plugins. Despite trying several solutions, such as incremental upgrades, downgrading your PHP version, and even removing the All-in-One SEO plugin, the error still persists.

The error message points to an issue with the ‘priority’ field in your database. Here’s a quick fix – you can rebuild the database tables. This is a known solution for this issue. You can do it by running this WP-CLI command: wp action-scheduler fix-schema. However, keep in mind that your hosting provider may not allow access to the WP-CLI. If that’s the case, you’ll need to get in touch with them for access.

?? Just a quick reminder: Before you make any changes, we strongly recommend that you create a backup of your full site and database. This is a crucial step to ensure that in case anything goes wrong, you can easily restore your site to its previous, functioning state.

I hope this helps resolve the issue you’re experiencing. If you have any further questions or if the problem persists, please don’t hesitate to get back in touch.

Hi Tamrat,

Thank you very much for a quick response.

I am running WordPress on a VPS server with Centos Web Panel installed on it, so I do have regular backups as well as access to WP-CLI or anything else you would suggest for me to try. And I forgot to mention that this was also something that I tried, but it just seemed to give me even more errors, so I turned away from this approach – I got scared I would break things even further. Would you suggest for me to just leave it running for now on old versions of these two plugins until the new version of WooCommerce and All-in-One SEO is released? Hopefully, the new version would fix these issues?

This is the error that I get after running the above command:

[root@srv1 emrah]# cd public_html
[root@srv1 public_html]# wp action-scheduler fix-schema
Error: YIKES! It looks like you’re running this as root. You probably meant to run this as the user that your WordPress installation exists under.

If you REALLY mean to run this as root, we won’t stop you, but just bear in mind that any code on this site will then have full control of your server, making it quite DANGEROUS.

If you’d like to continue as root, please run this again, adding this flag: –allow-root

If you’d like to run it as the user that this site is under, you can run the following to become the respective user:

sudo -u USER -i -- wp <command>

[root@srv1 public_html]# wp action-scheduler fix-schema –allow-root
PHP Warning: Undefined array key “HTTP_HOST” in /home/emrah/public_html/wp-content/plugins/force-https-littlebizzy/core/redirect.php on line 91
Warning: Undefined array key “HTTP_HOST” in /home/emrah/public_html/wp-content/plugins/force-https-littlebizzy/core/redirect.php on line 91
Warning: Some code is trying to do a URL redirect. Backtrace: 0 WP_CLI\Utils\wp_redirect_handler(https://) called at [/home/emrah/public_html/wp-includes/class-wp-hook.php:312] 1 WP_Hook->apply_filters(https://, Array ([0] => https://,[1] => 301)) called at [/home/emrah/public_html/wp-includes/plugin.php:205] 2 apply_filters(wp_redirect, https://, 301) called at [/home/emrah/public_html/wp-includes/pluggable.php:1396] 3 wp_redirect(https://, 301) called at [/home/emrah/public_html/wp-content/plugins/force-https-littlebizzy/core/redirect.php:91] 4 FHTTPS_Core_Redirect->redirect() called at [/home/emrah/public_html/wp-content/plugins/force-https-littlebizzy/core/redirect.php:68] 5 FHTTPS_Core_Redirect->start() called at [/home/emrah/public_html/wp-includes/class-wp-hook.php:310] 6 WP_Hook->apply_filters(, Array ([0] => )) called at [/home/emrah/public_html/wp-includes/class-wp-hook.php:334] 7 WP_Hook->do_action(Array ([0] => )) called at [/home/emrah/public_html/wp-includes/plugin.php:517] 8 do_action(plugins_loaded) called at [/home/emrah/public_html/wp-settings.php:495] 9 require(/home/emrah/public_html/wp-settings.php) called at [phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1349] 10 WP_CLI\Runner->load_wordpress() called at [phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php:1267] 11 WP_CLI\Runner->start() called at [phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php:28] 12 WP_CLI\Bootstrap\LaunchRunner->process(WP_CLI\Bootstrap\BootstrapState Object ([WP_CLI\Bootstrap\BootstrapStatestate] => Array ([context_manager] => WP_CLI\ContextManager Object ([WP_CLI\ContextManagercontexts] => Array ([cli] => WP_CLI\Context\Cli Object (),[admin] => WP_CLI\Context\Admin Object (),[frontend] => WP_CLI\Context\Frontend Object (),[auto] => WP_CLI\Context\Auto Object ([WP_CLI\Context\Autocontext_manager] => WP_CLI\ContextManager Object ( RECURSION)),[WP_CLI\ContextManagercurrent_context] => cli)))) called at [phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php:83] 13 WP_CLI\bootstrap() called at [phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php:32] 14 include(phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php) called at [phar:///usr/local/bin/wp/php/boot-phar.php:20] 15 include(phar:///usr/local/bin/wp/php/boot-phar.php) called at [/usr/local/bin/wp:4]

After analysing the error message, I disabled the severely outdated (no longer maintained) plugin called “force-https-littlebizzy” from the website, then ran the command and it was successful, this is the output that I got from the console:

[root@srv1 public_html]# wp action-scheduler fix-schema –allow-root
PHP Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 36
Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 36
PHP Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 39
Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 39
PHP Warning: Undefined array key “sp” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 39
Warning: Undefined array key “sp” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 39
PHP Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 42
Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 42
PHP Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 45
Warning: Undefined array key “query” in /home/emrah/public_html/wp-content/plugins/scanventory/classes/control.php on line 45
Success: Registered schema for ActionScheduler_LoggerSchema
Success: Registered schema for ActionScheduler_StoreSchema

Afterwards, I updated all plugins to the latest versions, and I updated the WooCommerce database, and it is all working well so far. I even returned PHP back to version 8.2.8. Above warnings are due to Scanventory. Scanventory is another severly outdated/no longer maintained plugin. Will have to consult with my client if they want to keep that plugin or if some alternative would be suitable.

Thanks a lot for your help Tamrat!

Moderator, please keep this topic open for a week, I will come back if the website starts acting up again due to this issue.

Hi @bostralian

It’s great to hear that you’ve successfully resolved the issue by disabling the outdated plugin and running the WP-CLI command. I’m thrilled to know that you’ve updated all your plugins to the latest versions, and your WooCommerce database is harmonizing well with PHP version 8.2.8.

The warnings you’re seeing indeed stem from the Scanventory plugin. If this plugin is severely outdated and lacks maintenance, it might trigger problems down the line. It would be wise to talk to your client about potentially swapping it out for a more current and actively maintained plugin.

Thanks for updating us on your progress and solution. As you requested, we’ll leave this topic open for a week. Should you run into any more issues or have more questions, feel free to reach out. We’re always here to assist you!