version 3 problems with database prefix

Resolved

(@phloo)

Unable to purge the cache since our database doesn’t use the default wordpress db prefix (“wp_”).

Error is:

WordPress-Database-Error Table 'wp_sitename.XXXXXX_fvm_cache' doesn't exist TRUNCATE TABLE XXXXXX_fvm_cache von include('phar:///usr/local/bin/wp/php/boot-phar.php'), include('phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php'), WP_CLI\bootstrap, WP_CLI\Bootstrap\LaunchRunner->process, WP_CLI\Runner->start, WP_CLI\Runner->run_command_and_exit, WP_CLI\Runner->run_command, WP_CLI\Dispatcher\Subcommand->invoke, call_user_func, WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}, call_user_func, fastvelocity_WPCLI->purge, fvm_purge_minification
WordPress-Database-Error Table 'wp_sitename.XXXXXX_fvm_logs' doesn't exist for Query TRUNCATE TABLE XXXXXX_fvm_logs von include('phar:///usr/local/bin/wp/php/boot-phar.php'), include('phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php'), WP_CLI\bootstrap, WP_CLI\Bootstrap\LaunchRunner->process, WP_CLI\Runner->start, WP_CLI\Runner->run_command_and_exit, WP_CLI\Runner->run_command, WP_CLI\Dispatcher\Subcommand->invoke, call_user_func, WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}, call_user_func, fastvelocity_WPCLI->purge, fvm_purge_minification

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Author Raul P.
(@alignak)

5 years, 4 months ago

I don’t use wp_ for the database, I use $wpdb->prefix which is correct.

But for some reason the tables were not created on the update routine.
Did you update directly from wp-admin, or did you perhaps upload the files separatly?

Can you disable and reenable the plugin and see if the error still shows up?
Disabling and enabling the plugin, should trigger the tables creation.

Thanks
Thread Starter phloo
(@phloo)

5 years, 4 months ago
hi Raul, deactivating and re-enabling seemed to be the fix
```
Success: FVM: All Caches are now cleared. (Tue, 29 Dec 2020 @ 12:10:19 UTC)
Success: A cache purge request has been sent to <strong>WP Engine</strong>
http_request_async curl error: Failed to connect to localhost port 80: Connection refused
Warning: Expired minification files are set to be deleted in 24 hours.
```
Plugin Author Raul P.
(@alignak)

5 years, 4 months ago

Thanks for reporting.

As for the http_request_async error, we don’t use it on FVM, but it’s caused by the WP Engine plugin when we send a cache purge request to wp engine (likely you are not using their cdn).

https://wordpress.org/support/topic/wp-cli-command-returns-timeout/

You can ignore it until they fix it.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘version 3 problems with database prefix’ is closed to new replies.