Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
litespeed_wiki:cache:lscwp:faq [2017/11/02 14:05] Eric Leu [Are my images optimized?] |
litespeed_wiki:cache:lscwp:faq [2020/11/14 15:37] (current) Lisa Clarke Redirect to new Documentation Site |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======LSCWP Frequently Asked Questions====== | + | ~~REDIRECT>https://docs.litespeedtech.com/lscache/lscwp/faq/~~ |
- | + | ||
- | =====Is the LiteSpeed Cache Plugin for WordPress free?===== | + | |
- | + | ||
- | Yes, LSCWP will always be free and open source. That said, a LiteSpeed server is required, and there are fees associated with some LiteSpeed server editions (see question 2). | + | |
- | + | ||
- | =====What server software is required for this plugin?===== | + | |
- | + | ||
- | A LiteSpeed server is required in order to use this plugin. | + | |
- | - LiteSPeed Web Server Enterprise with LSCache Module (v5.0.10+) | + | |
- | - OpenLiteSpeed (v1.4.17+) | + | |
- | - LiteSpeed WebADC (v2.0+) | + | |
- | + | ||
- | Any single server or cluster including a LiteSpeed server will work. | + | |
- | + | ||
- | =====Does this plugin work in a clustered environment?===== | + | |
- | + | ||
- | The cache entries are stored at the LiteSpeed server level. The simplest solution is to use LiteSpeed WebADC, as the cache entries will be stored at that level. | + | |
- | + | ||
- | If using another load balancer, the cache entries will only be stored at the backend nodes, not at the load balancer. | + | |
- | + | ||
- | The purges will also not be synchronized across the nodes, so this is not recommended. | + | |
- | + | ||
- | If a customized solution is required, please contact LiteSpeed Technologies at info@litespeedtech.com | + | |
- | + | ||
- | NOTICE: The rewrite rules created by this plugin must be copied to the Load Balancer. | + | |
- | + | ||
- | =====Where are the cached files stored?===== | + | |
- | + | ||
- | The actual cached pages are stored and managed by LiteSpeed Servers. | + | |
- | + | ||
- | Nothing is stored within the WordPress file structure. | + | |
- | + | ||
- | =====Does LiteSpeed Cache for WordPress work with OpenLiteSpeed?===== | + | |
- | + | ||
- | Yes it can work well with OpenLiteSpeed, although some features (such as ESI) may not be supported. Any setting changes that require modifying the .htaccess file will require a server restart. | + | |
- | + | ||
- | =====Is WooCommerce supported?===== | + | |
- | + | ||
- | In short, yes. However, for some woocommerce themes, the cart may not be updated correctly. Please [[https://blog.litespeedtech.com/2017/05/31/wpw-fixing-lscachewoocommerce-conflicts/|see this blog post]] for a quick tutorial on how to detect this problem and fix it if necessary. | + | |
- | + | ||
- | =====My plugin has some pages that are not cacheable. How do I instruct the LiteSpeed Cache Plugin to not cache the page?===== | + | |
- | + | ||
- | As of version 1.0.10, you may simply add ''define('LSCACHE_NO_CACHE', true);'' sometime before the shutdown hook, and it should be recognized by the cache. | + | |
- | + | ||
- | Alternatively, you may use the function ''xxxLiteSpeed_Cache_Tags::set_noncacheable();'' for earlier versions (1.0.7+). | + | |
- | + | ||
- | If using the function, make sure to check that the class exists prior to using the function. | + | |
- | + | ||
- | Please see [[litespeed_wiki:cache:lscwp:api|this article]] for more information and to learn what else you can do to integrate your plugin with LSCWP. | + | |
- | + | ||
- | =====Are my images optimized?===== | + | |
- | + | ||
- | If you want to optimize your images, we recommend use [[https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:lscwp:image-optimization | Image-Optimize function]] | + | |
- | =====How do I get WP-PostViews to display an updating view count?===== | + | |
- | + | ||
- | Use | + | |
- | <code> | + | |
- | <div id="postviews_lscwp"></div> | + | |
- | </code> | + | |
- | to replace | + | |
- | + | ||
- | <code> | + | |
- | <?php if(function_exists('the_views')) { the_views(); } ?> | + | |
- | </code> | + | |
- | **NOTE:** The id can be changed, but the div id and the ajax function must match. | + | |
- | + | ||
- | Replace the ajax query in wp-content/plugins/wp-postviews/postviews-cache.js with | + | |
- | + | ||
- | <code> | + | |
- | jQuery.ajax({ type:"GET", url:viewsCacheL10n.admin_ajax_url, | + | |
- | data:"postviews_id="+viewsCacheL10n.post_id+"&action=postviews", | + | |
- | cache:!1, success:function(data) { | + | |
- | if(data) { jQuery('#postviews_lscwp').html(data+' views'); } } }); | + | |
- | </code> | + | |
- | + | ||
- | Purge the cache to use the updated pages. | + | |
- | + | ||
- | =====How do I enable the crawler?===== | + | |
- | + | ||
- | The crawler is disabled by default, and must be enabled by the server admin first. | + | |
- | + | ||
- | Once the crawler is enabled on the server side, navigate to **LiteSpeed Cache > Crawler** and set **Activation** to ''Enable''. | + | |
- | + | ||
- | For more detailed information about crawler setup, please see [[https://blog.litespeedtech.com/2017/06/14/wpw-crawl-your-site-make-it-fly/|our blog post]]. | + |