NP Quote Request WooCommerce Table Doesn’t Exist

it should have been created after the update. it might be a database permission issue to create it. Please try this:
inactivate and deactivate the plugin. it should create the table if it does not exist.
it would be helpful to enable WordPress debug so we can see the errors in the log file.

Can you enable WordPress debug in wp-config.php by adding

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define( ‘WP_DEBUG_DISPLAY’, false );

to your wp-config.php

Find wp-config.php in your WordPress directory and copy and paste the 3 lines above in that file. Make sure none of the lines are repeated in the file.
deactivate and inactivate the plugin and check the debug.log file in the wp-content directory.

Hi,
Just checking if the issue has been resolved.

Looks like that did the trick. I don’t see the error any longer. Thank you. Will try your recommendations if it returns.

thanks for the feedback.

Hi,
I’m having the same issue.

WordPress database error: [Table ‘ics_dev.wp_npxyz2021_sessions’ doesn’t exist]
UPDATE wp_npxyz2021_sessions set expiration= ‘1639796815’ where option_name = ‘_rfqtk_wp_session_4da546c60f89c28be8411cf999939575’

I’ve deactivated / reactivated the plugin, deleted and reinstalled but not having any success. Do you have any other suggestions??

if you have access to the database, run the following sql code to create the table. maybe there is a permission issue and WordPress is not able to create the table during activation. you can use this plugin WP Data Access.

CREATE TABLEwp_npxyz2021_sessions` (
option_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
option_name varchar(191) NOT NULL,
option_value longtext NOT NULL,
expiration bigint(20) NOT NULL,
misc_value longtext,
created timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
updated timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (option_id),
UNIQUE KEY option_name (option_name)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;`

Hi, thanks for the fast reply.

Tried to run command but getting error below. MYSQL version 5.1.73

#1064 – You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘TABLEmp_npxyz2021_sessions` (
option_id bigint(20) unsigned NOT NULL AUTO_INCR’ at line 1

Also tried changing option_id line to below but still didn’t work.

CREATE TABLEmp_npxyz2021_sessions` (
option_id bigint(20) NOT NULL AUTO_INCREMENT PRIMARY KEY,
option_name varchar(191) NOT NULL,
option_value longtext NOT NULL,
expiration bigint(20) NOT NULL,
misc_value longtext,
created timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
updated timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (option_id),
UNIQUE KEY option_name (option_name)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;`

try this one. your is not the same. make sure there is a space between table
and wp_npxyz2021_sessions

CREATE TABLE wp_npxyz2021_sessions (
option_id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
option_name varchar(191) NOT NULL,
option_value longtext NOT NULL,
expiration bigint(20) NOT NULL,
misc_value longtext,
created timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
updated timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
PRIMARY KEY (option_id),
UNIQUE KEY option_name (option_name)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Okay thanks.
New error now..
#1293 – Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause

your MySQL version is kind of old 5.1.73. this is a limitation that has been lifted as of MySQL 5.6.5. I suggest you upgrade at least to that. this probably why it did not work on activation.

You can try updating to 1.8.279. we have made an attempt to make it backward compatible with MySQl 5.1. But 5.1 will likely still give incompatibility problems down the road. Hope this works.

The site is running on a very old Centos 6 server so it was a little problematic to update MySQL using default yum updates. However I’ve managed to manually update it this morning so now running 6.5 and was able to successfully update the database with the new tables.

Thanks for the great support. Much appreciated!!

6.5 will give you a lot less trouble ??