Notice about v1.3.1 optimizer
-
For those who have css/js optimizer issue’s users:
Please try to reinstall v1.3.1. We just improved the compatibility in latest build.
The latest build of v1.3.1 fixed the css/js optimizer compatibility issue.
In the rare case that the issue is not yet resolved, please try the following:
If you meet an issue that the css/js optimizer can’t work properly in v1.3.1, please check if your WordPress MySQL account has enough access to create tables.
If not, please try to run this manually in MySQL. You can do this by PHPMyAdmin:
Note: please change
wp_
inwp_litespeed_optimizer
to your wordpress tables prefix.CREATE TABLE IF NOT EXISTS wp_litespeed_optimizer (
id int(11) 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)
);We will add a check in next release, to make sure if this table isn’t created, the optimizer options can’t be turned on.
- The topic ‘Notice about v1.3.1 optimizer’ is closed to new replies.