Wordpress LScache Plugin: Error after update to v3: Failed to create table cssjs!
Last Updated on: Wed, 15 Apr 2026 00:00:02 Gday support team, Very happy with the plugin. Just updated the plugin to V3 and getting the following error: Failed to create table cssjs! SQL: CREATE TABLE IF NOT EXISTS wp_litespeed_cssjs (id bigint(20) NOT NULL AUTO_INCREMENT, hash_name varchar(60) NOT NULL COMMENT hash.filetype , src text NOT NULL COMMENT full url array set , dateline int(11) NOT NULL, refer varchar(255) NOT NULL COMMENT The container page url , PRIMARY KEY (id), UNIQUE KEY hash_name (hash_name), KEY dateline (dateline) ) DEFAULT CHARACTER SET utf8mb4 COLLATE UXmos-7F1H]T . Could you please help resolve this? Thank you, Ian Your mysql COLLATE UXmos-7F1H]T generated by WP is pretty strange. We can try to debug on it. Can you come to slack and pm me after 10pm EST? thx. I got the same message, was only able to add these to the server manually by removing the comments. Mysql is Server version: 8.0.19 Source distribution ? in this instance its Digitaloceans managed database Update: Interestingly enough even though Ive added the table manually to the correct database on the managed database, im still getting the error as if the table doesnt exist. Reason: update Same error, I just update Cpanel and I update litespeed. And I dont have CSS/jss minify settings page in Litespeed Mysql is Server version: 8.0.19 Source distribution ? in this instance its Digitaloceans managed database I am getting the same error Failed to create table cssjs! SQL: CREATE TABLE IF NOT EXISTS wp_litespeed_cssjs (id bigint(20) NOT NULL AUTO_INCREMENT, hash_name varchar(60) NOT NULL COMMENT hash.filetype , src text NOT NULL COMMENT full url array set , dateline int(11) NOT NULL, refer varchar(255) NOT NULL COMMENT The container page url , PRIMARY KEY (id), UNIQUE KEY hash_name (hash_name), KEY dateline (dateline) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci . @dikibhuyan Im encountering the same issue with a DO Managed DB. Did you manage to solve it? @psanma nope .. lol I just switched to wp-rocket
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference