Error after update to v3: Failed to create table cssjs!

Resolved Ian
(@ipgill)

6 years, 1 month ago

G’day 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

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

Plugin Support Hai Zheng⚡
(@hailite)

6 years, 1 month ago

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.
Jeroenv3
(@jeroenv3)

6 years ago
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 it’s Digitalocean’s managed database

Update: Interestingly enough even though I’ve added the table manually to the correct database on the managed database, i’m still getting the error as if the table doesn’t exist.
- This reply was modified 6 years ago by Jeroenv3. Reason: update
dewinbrush
(@dewinbrush)

6 years ago

Same error, I just update Cpanel and I update litespeed. And I don’t have CSS/jss minify settings page in Litespeed

dikibhuyan
(@dikibhuyan)

5 years, 10 months ago

Mysql is Server version: 8.0.19 Source distribution – in this instance it’s Digitalocean’s 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;.

PSanma
(@psanma)

5 years, 9 months ago

@dikibhuyan I’m encountering the same issue with a DO Managed DB. Did you manage to solve it?

dikibhuyan
(@dikibhuyan)

5 years, 7 months ago

@psanma nope .. lol I just switched to wp-rocket