![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/null-7.jpeg\" "\\"\\"")
<\/p>\n<\/p>\n
Welcome to another installment of WordPress Wednesday<\/a>!<\/p>\n Disclaimer<\/i><\/b>: The information contained in this post is accurate for LSCWP v1.4<\/span><\/i>. If you are using a newer version of the plugin, some details may have changed. Please<\/span><\/i> refer to our wiki<\/span><\/i><\/a> for the latest!<\/span><\/i><\/p>\n In most of our previous posts we\u2019ve talked to site owners and hosting providers. Today, we\u2019d like to address our fellow plugin developers. Let\u2019s talk about how to ensure your plugin is compatible with LiteSpeed Cache for WordPress.<\/strong> And for those of you who are developers and would like to help make someone else<\/em>\u2019s plugin work well with LSCache, you\u2019ll want to check out \u201cWhat if it\u2019s not your plugin?<\/a>\u201d below.<\/p>\n To know if your plugin is compatible with LSCache, it helps to understand a bit about caching in general, as well as LiteSpeed Cache in particular. For that, we recommend you have a look at our Caching 101 series<\/a>.<\/p>\n If your plugin doesn\u2019t generate site content, or do anything out of the ordinary with existing front-end content, then chances are it is 100% compatible with LiteSpeed Cache for WordPress already. The vast majority of plugins will fall into this \u201calready compatible\u201d category. If, however, you have a plugin that makes changes to front-end-displayed content, and it does so in a non-traditional way, you\u2019ll want to read on.<\/p>\n LSCWP purges pages from the cache when certain events are triggered. If your plugin generates content that triggers those same events, then we\u2019re already compatible in that area.<\/p>\n LSCWP follows a set of rules to determine whether a page is cacheable. If your plugin generates content that also abides by those same rules, then we\u2019re already compatible in that area as well.<\/p>\n Even if your plugin generates cacheable content that doesn\u2019t<\/em> trigger the standard events, or it generates non-cacheable content that doesn\u2019t<\/em> abide by the same rules that we do, we can still get along. You may just need to invoke our API<\/a> first.<\/p>\n First, let\u2019s look at purging rules and exclude rules to understand what is possible, and then we can look at the API functions that allow you to realize those possibilities.<\/p>\n LSCache will automatically purge a page from the cache if any of the following events are triggered:<\/p>\n LSCache\u2019s \u201csmart purge\u201d feature works by assigning tags to each cacheable page, and then using those tags to intelligently group together a collection of pages to be purged later.<\/p>\n In its most basic form, each page is tagged with its Post ID, and then sent to the server to be cached. When one of the above events is triggered for the page, that request will notify the server to purge all of the cache\u2019s items that are also tagged with that page\u2019s Post ID. Depending on the purge rules that have been defined by the site owner, this could include related category pages, tag pages, and monthly archives, among other things.<\/p>\n If your plugin makes modifications that trigger those same events, then you should be good. If, however, you have an application that changes what appears on a page without triggering any of those events, then you will need to inform LiteSpeed Cache that a purge is necessary.<\/p>\n Our API gives you the ability to customize the notifications sent to the server. As the page is stored in the cache, you can assign your own tags to the page so that later, it may be purged as part of a custom group. Multiple tags can be set on a single page, and a single tag may be used on multiple pages. This many-to-many mapping provides a flexible system enabling you to group pages in a variety of useful ways.<\/p>\n If a change is made where all pages tagged For this functionality, you\u2019ll want to pay special attention to the API functions TIP<\/strong>: When defining tags, it is a good idea to give them a prefix that is unique to your application, that way you avoid stepping on anyone else\u2019s tags. In this example, we\u2019ve used As of v1.4, LSCache considers a page to be non-cacheable if<\/p>\n If your plugin generates content that is non-cacheable but doesn\u2019t fall into one of the above categories, you will need to inform LiteSpeed Cache that the content cannot be cached. Our API gives you the ability to do so via the LiteSpeed Cache for WordPress\u2019 API provides functions and hooks that allow you to customize the aspects of cache management that we discussed above. Listed below are eight useful API functions and hooks. There is more to our API, though, and you can get all of the latest details and available functions on our wiki<\/a>.<\/p>\n These functions are defined in Use these functions to implement your own purge rules, as in our forum\/group\/state example above.<\/p>\n If you plugin generates content that should not be cached, use these functions to implement your own exclude rules.<\/p>\n If your plugin makes adjustments to content through WordPress Admin (for example, you change a product description and then need to purge that product) these are the functions to use.<\/p>\n If you\u2019d like to use ESI blocks<\/a> in your plugin, you\u2019ll want to employ the following functions:<\/p>\n For some detailed ESI examples, visit our wiki<\/a>.<\/p>\n Not every plugin author is interested in modifying their plugin for LSCache compatibility, and that\u2019s ok. You don\u2019t have to be the author of the plugin to make sure it is compatible with LiteSpeed Cache. In fact, we\u2019ve been adding support for well-known plugins ourselves since the beginning.<\/p>\n If you are currently using an incompatible plugin, and you have some PHP skills, you can contribute to our project. Take a look at our plugin source code, and you\u2019ll see a And then get in touch<\/a>! We\u2019d love to integrate your working solution into our plugin so that everyone may benefit.<\/p>\n The majority of plugins get along just fine with LSCache, and those that don\u2019t <\/em>generally just need a line or two of code to make them compatible. If the advice we\u2019ve shared today doesn\u2019t help you with your particular application, or you\u2019d like to discuss any of these ideas in more depth, feel free to get in touch with us! Visit the WordPress support forum for LSCache<\/a>, or go through our ticket system<\/a>. We\u2019d be happy to help.<\/p>\n — Don\u2019t forget to meet us back here next week for the next installment. In the meantime, here are a few other things you can do:<\/p>\n Is your plugin compatible with LSCWP? Find out! And if it’s not, use our API to make it so.<\/p>\n","protected":false},"author":1,"featured_media":8350,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[28],"tags":[38,316,317],"class_list":["post-8348","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cache","tag-api","tag-wordpress","tag-wordpress-wednesday"],"jetpack_featured_media_url":"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/null-7.jpeg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/posts\/8348","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/comments?post=8348"}],"version-history":[{"count":0,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/posts\/8348\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/media\/8350"}],"wp:attachment":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/media?parent=8348"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/categories?post=8348"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/tags?post=8348"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Are we compatible?<\/h2>\n
Purge rules<\/h2>\n
![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/null-8.jpeg\" "\\"\\"")
<\/p>\n\n
Example:<\/h3>\n
\n
MTPP_F.1, MTPP_G.4, MTPP_S.wyoming<\/code> (because the page is in forum 1, group 4, and related to the state of Wyoming).<\/li>\nMTPP_F.1, MTPP_G.2, MTPP_S.iowa<\/code> (because the page is in forum 1, group 2, and related to the state of Iowa).<\/li>\n<\/ul>\nMTPP_F.1<\/code> need to be purged, the tag system enables the server to easily purge both Page #1 and Page #2. If a request is sent to the server indicating that pages tagged MTPP_S.wyoming<\/code> need to be purged, then the tagging system knows to only purge Page #1.<\/p>\ntag_add<\/code> and purge<\/code>.<\/p>\nMTPP_<\/code> for \u201cmy third-party plugin.\u201d<\/p>\nExclude rules<\/h2>\n
![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/null-9.jpeg\" "\\"\\"")
<\/p>\n\n
is_trackback()<\/code> is true<\/li>\nis_search()<\/code> is true<\/li>\nhook_control<\/code> and set_nocache<\/code> API hook and function.<\/p>\nAPI<\/h2>\n
![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/null-10.jpeg\" "\\"\\"")
<\/p>\nplugins\/litespeed-cache\/includes\/litespeed-cache-api.class.php<\/code> and may be used in any hook point prior to the shutdown<\/code> hook point.<\/p>\nCustomized Purging<\/h3>\n
\n
LiteSpeed_Cache_API::tag_add($tag)<\/code>
\nWhen a page is created or edited, use this function to add a single cache tag (or group of cache tags) to the list of cache tags associated with the current page. These tags are appended the list of built-in tags generated by LSCWP.<\/li>\nLiteSpeed_Cache_API::purge($tag)<\/code>
\nWhen you need to purge a page and its related pages, use this function to add a single purge tag (or group of purge tags) to the list of tags to be purged with the request.<\/li>\n<\/ul>\nCustomized Exclusions<\/h3>\n
\n
LiteSpeed_Cache_API::set_nocache()<\/code>
\nUse this function to mark the current page as non-cacheable.<\/li>\nLiteSpeed_Cache_API::hook_control($hook)<\/code>
\nSpecify a hook for cache control with this filter. The hook will be triggered when the cache plugin is checking whether the current page is cacheable. This filter will not<\/em> trigger on admin pages nor any page that has previously been marked as non-cacheable.<\/li>\n<\/ul>\nCustomized Admin Handling<\/h3>\n
\n
LiteSpeed_Cache_API::purge_post($id)<\/code>
\nPurge a single post by id with this function.<\/li>\nLiteSpeed_Cache_API::hook_purge($hook)<\/code>
\nThis hook is called at the end of every cacheable request, and gives you the ability to add purge tags to the current request.<\/li>\n<\/ul>\nESI Blocks<\/h3>\n
\n
LiteSpeed_Cache_API::esi_url($block_id, $wrapper, $params = array(), $control = 'private,no-vary')<\/code>
\nCreates a new ESI block. Use this if you wish to punch a hole for differently-cached content (i.e. a privately-cached individualized greeting on a publicly-cached page).<\/li>\nLiteSpeed_Cache_API::hook_tpl_esi($block, $hook)<\/code>
\nUse this hook to display an ESI block.<\/li>\n<\/ul>\nWhat if it\u2019s not your plugin?<\/h2>\n
![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/null-11.jpeg\" "\\"\\"")
<\/p>\nthirdparty<\/code> directory where you\u2019ll find our current integrations. Use these examples to help you write up some code that will make your own favorite plugin compatible with LSCache.<\/p>\nConclusion<\/h2>\n
\nHave some of your own ideas for future WordPress Wednesday<\/a> topics? Leave us a comment!<\/p>\n\n