Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
litespeed_wiki:cache:lscwp:installation [2018/03/15 10:10]
Tihomir [WordPress Lacks Permissions] 		litespeed_wiki:cache:lscwp:installation [2020/11/14 15:39] (current)
Lisa Clarke Redirect to new Documentation Site
Line 1: Line 1:
-====== Installing & Enabling The LSCache Plugin For WordPress ====== +~~REDIRECT>​https://​docs.litespeedtech.com/lscache/​lscwp/​installation/​~~
- +
- +
-===== Pre-Installation Requirements ===== +
- +
-  * LiteSpeed Web Server Enterprise Edition 5.0.10+. +
-  * LSCache Module. (Included with a 2-CPU or higher license. Can be purchased as an add-on for VPS, Ultra VPS, and 1-CPU licenses.) +
- +
-===== Installation ===== +
- +
-  - Configure server-level and/or virtual-host-level cache root and cache policy by selecting your setup in the Web Server Configuration section of the [[litespeed_wiki:​cache:​common_installation#​web_server_configuration|LiteSpeed Web Cache Common Installation Guide]]. +
-  - Disable any other page caches as these will interfere with LSCWP.<​sup>​*</​sup> +
-  - [[https://wordpress.org/​plugins/​litespeed-cache/​|Download the LSCWP plugin]] from our WordPress Plugin Directory page. +
-  - Log in to your WordPress Dashboard, navigate to **Plugins > Add New** and click on **Upload Plugin**. +
-  - Select the LSCWP zip file and click **Install Now**. Activate the plugin. +
-  - Navigate to **LiteSpeed Cache > Settings > General** and set **Enable LiteSpeed Cache** to ''​Enable''​. +
- +
-You may also install the plugin directly from the **Plugins > Add New** screen. Replace steps 3-5 above with: +
-  * Search for ''​LiteSpeed Cache''​ in the search box. Our plugin should be the first search result to come up. +
-  * Press **Install Now**. Activate the plugin. +
- +
-* Please see [[litespeed_wiki:​cache:​lscwp:​customizations:​multi-cache-plugins|this wiki article]] for assistance using multiple optimization plugins at once. +
- +
-===== Testing ===== +
- +
-You can verify a page is being served from LSCWP through the following steps:  +
-    - Open the developer tools on a //​non-logged-in browser// and navigate to your site. Open the **Network** tab. +
-    - Refresh the page. +
-    - Click the first resource (this should be an HTML file and the resource'​s headers should appear as in the image below). For example, if your page is ''<​nowiki>​http://​example.com/wordpress/</​nowiki>'',​ your first resource should either be something like ''​example.com/​wordpress/''​ or ''​wordpress/''​.{{:​litespeed_wiki:​cache:​lscwp:​wpcachetest.png?​direct&​900|}} +
-  - In a different, ​//logged-in browser//, in your WordPress Dashboard, navigate to **LiteSpeed Cache > Manage** and click the **Purge All** button.  +
-  - Reload the page in the first (non-logged-in) browser and select the same resource again. If you see headings similar to <​code>​ +
-X-LiteSpeed-Cache:​ miss +
-X-LiteSpeed-Cache-Control:​public,​max-age=1800 +
-X-LiteSpeed-Tag:​B1_F,​B1_ </​code>​(for example), this means the page had not yet been cached, but that LiteSpeed has now stored it for future use. +
-  - Reload the page a second time and you should see ''​X-LiteSpeed-Cache:​ hit''​ in the response header. This means the page is being served by the cache and LSCWP is configured correctly. +
- +
-**Note:** If your first refresh after purging returns ''​X-LiteSpeed-Cache:​ hit''​ in the response header, this may be because someone else visited the page //after// you purged but //before// you refreshed it yourself. Try again from step 4. +
- +
-===== Good to Know ===== +
- +
-Here are a few other things that may may be useful for your installation. +
- +
-==== Turning On the WordPress Debug Log ==== +
- +
-To enable the WordPress debug log, modify ''​wp-config.php''​ under WordPress'​ root directory as follows: +
- +
-  - Set ''​WP_DEBUG''​ to true. \\  \\ <​code>​define('​WP_DEBUG',​true);<​/code> +
-  - Add the following: \\ \\ <​code>​define('​WP_DEBUG_LOG',​true);</​code>​ +
- +
-A ''​debug.log''​ file will be generated under the ''​wp-content''​ directory, and will log information whenever WordPress hits the backend.  +
- +
-You can monitor this log during debugging using the following command: +
-  tail -f wp-content/​debug.log +
-   +
- +
-==== Multiple LiteSpeed Cache Plugins ==== +
- +
-If you are using any of our other LiteSpeed Cache plugins for other web apps (like Magento, PrestaShop, XenForo, etc), or you are running multiple instances of WordPress, please see [[litespeed_wiki:​cache:​common:​logged-in-cookie-conflicts|this article]] for some important information about avoiding conflicts between the different apps' caches. +
-   +
-==== WordPress Lacks Permissions ==== +
- +
-If WordPress doesn'​t have access to create tables in your database, please run these SQL queries manually after installation:​ +
- +
-<code sql> +
-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) +
-);</​code>​ +
- +
-and +
- +
-<code sql> +
-CREATE TABLE IF NOT EXISTS `wp_litespeed_img_optm` ( +
-  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,​ +
-  `post_id` bigint(20) unsigned NOT NULL DEFAULT '​0',​ +
-  `optm_status` varchar(64) NOT NULL DEFAULT '',​ +
-  `src` varchar(1000) NOT NULL DEFAULT '',​ +
-  `srcpath_md5` varchar(128) NOT NULL DEFAULT '',​ +
-  `src_md5` varchar(128) NOT NULL DEFAULT '',​ +
-  `server` varchar(255) NOT NULL DEFAULT '',​ +
-  `root_id` int(11) NOT NULL DEFAULT '​0',​ +
-  `src_filesize` int(11) NOT NULL DEFAULT '​0',​ +
-  `target_filesize` int(11) NOT NULL DEFAULT '​0',​ +
-  `target_saved` int(11) NOT NULL DEFAULT '​0',​ +
-  `webp_filesize` int(11) NOT NULL DEFAULT '​0',​ +
-  `webp_saved` int(11) NOT NULL DEFAULT '​0',​ +
-  PRIMARY KEY (`id`), +
-  UNIQUE KEY `post_id_2` (`post_id`,​`srcpath_md5`),​ +
-  KEY `post_id` (`post_id`),​ +
-  KEY `optm_status` (`optm_status`),​ +
-  KEY `root_id` (`root_id`),​ +
-  KEY `src_md5` (`src_md5`),​ +
-  KEY `srcpath_md5` (`srcpath_md5`) +
-  );</​code>​ +
- +
-**Note:** If your site uses a table prefix other than ''​wp_'',​ please replace the ''​wp_''​ in ''​wp_litespeed_optimizer''​ with your site's prefix.+
  • Admin
  • Last modified: 2018/03/15 10:10
  • by Tihomir