{"id":7884,"date":"2017-08-23T06:00:39","date_gmt":"2017-08-23T10:00:39","guid":{"rendered":"https:\/\/blog.litespeedtech.com\/?p=7884"},"modified":"2017-08-23T06:00:39","modified_gmt":"2017-08-23T10:00:39","slug":"wpw-litespeed-cache-post-types-and-taxonomies","status":"publish","type":"post","link":"https:\/\/lswp.store\/index.php\/2017\/08\/23\/wpw-litespeed-cache-post-types-and-taxonomies\/","title":{"rendered":"WpW: LiteSpeed Cache, Post Types and Taxonomies"},"content":{"rendered":"

\"\"<\/p>\n

Welcome to another installment of WordPress Wednesday<\/a>!<\/p>\n

Last week we explored the often misunderstood concepts of Post Types and Taxonomies<\/a> in WordPress. This week, we are going to relate that to our LiteSpeed Cache plugin. How does LSCWP handle Post Types and Taxonomies, both the built-in kinds and the custom ones? .<\/p>\n

You know from our last article<\/a> that WordPress consists of seven post types and four taxonomies by default (as of this writing), plus any custom post types and taxonomies you or your plugins may have added.<\/p>\n

LiteSpeed Cache for WordPress caches all post types and post-related taxonomies, even custom ones.<\/b><\/p>\n

Additionally, when it comes to managing <\/i>the cache, there are a few places where post type and taxonomy come into play.<\/p>\n

Purging by Taxonomy<\/h2>\n

You can purge two built-in taxonomies from the cache on demand: category and tag.<\/p>\n

From your WordPress dashboard, navigate to LiteSpeed Cache > Manage<\/b>, scroll down to Purge By\u2026<\/b> and select either Category<\/code> or Tag<\/code>. Enter the name(s) of the category or tag that you wish to purge.<\/p>\n

It is not currently possible to manually purge any taxonomies other than category or tag from the cache.<\/p>\n

Auto Purging<\/h2>\n

One of LSCache\u2019s most powerful features is its ability to auto-purge certain pages based on a set of rules. These rules say: \u201cwhen a post is updated or published, purge these other pages that are related to the post.\u201d<\/p>\n

\"\"<\/p>\n

See the Post type archive<\/code> and Term archive<\/code> options up there? If you select those, then your custom post types and your custom taxonomies will be included in an automatic purge.<\/p>\n

Remember last week\u2019s example? We put our discussion of custom post types and taxonomies in the context of your fictitious automotive review site. We said that you had a custom post type \u201cReview\u201d and custom taxonomies \u201cModel Year,\u201d \u201cMake\u201d and \u201cModel.\u201d<\/p>\n

Continuing with that example, if you were to update your review of the 2013 Chevy Impala, then that post would be purged, along with the post type archive (review), and the taxonomy\/term archives (2013, chevrolet, and impala). To access these settings, from your WordPress dashboard, navigate to LiteSpeed Cache > Settings > Purge Rules<\/b>.<\/p>\n

Do Not Cache Rules for Custom Post Types and Taxonomies<\/h2>\n

If you have post types that you do not<\/i> want to be cached, you can define rules to exclude them. From your WordPress dashboard, navigate to LiteSpeed Cache > Settings > Do Not Cache Rules<\/b>.<\/p>\n

You can exclude particular categories by listing the relevant category IDs in the Category List<\/b> box.<\/p>\n

You can exclude particular tags by listing the relevant tag IDs in the Tag List<\/b> box.<\/p>\n

You can exclude custom taxonomies (and post types) as well, if your permalink structure supports it, but it\u2019s not quite as simple. You need to use the URI List<\/b>. To determine what to enter in the box, you\u2019ll have to look at the structure of your permalinks. Let\u2019s say your permalinks are in this format:<\/p>\n

\nhttp:\/\/www.yourdomain.com\/custom-post-type\/custom-taxonomy\/term\/post-title\n<\/pre>\n
for example:<\/p>\n
\nhttp:\/\/www.yourautoreviewsite.com\/reviews\/makes\/chevrolet\/reviewing-2013-chevy-impala\n<\/pre>\n
If you wanted to exclude all of your reviews from being cached, you\u2019d enter \/reviews\/<\/code> in the URI List<\/b>.<\/p>\n
If you only wanted to exclude reviews of Chevrolets, then you\u2019d enter \/reviews\/makes\/chevrolet\/<\/code> in the URI List<\/b>.<\/p>\n
\"\"<\/p>\n
URI List<\/b> does a prefix match to relative links, meaning it matches whatever strings you enter to the beginning of the URLs (minus the domain names).<\/p>\n
So, using the example URL above, if you enter \/reviews\/makes\/chevrolet\/<\/code> it will match \/reviews\/makes\/chevrolet\/reviewing-2013-chevy-impala<\/code>, and \/reviews\/makes\/chevrolet\/reviewing-2006-chevy-uplander<\/code> but not \/reviews\/makes\/pontiac\/reviewing-2006-pontiac-montana<\/code>.<\/p>\n
Your permalinks may be set up differently than this, but hopefully there is something<\/i> about them that can differentiate them enough from your other content. Use that difference to single out a prefix for the URI List<\/b> box.<\/p>\n
Crawling<\/h2>\n
If the crawler is enabled on your site, then your custom post types are already included in the crawl. You can exclude them, if you like.<\/p>\n
From the WordPress dashboard, navigate to LiteSpeed Cache > Settings > Crawler<\/b>. Under the Exclude Custom Post Types<\/b> input box, you will see a list of available custom post types. Enter the ones you want to exclude, one line at a time, and they will not be crawled.<\/p>\n
And there you have it. LiteSpeed Cache for WordPress caches all built-in and custom post types, which is great news! And for those special cases, where you don\u2019t want certain post types to be cached, LSCWP provides mechanisms that allow you to manage those cases. Be sure to leave a comment if you have any questions about this topic!<\/p>\n
—<\/p>\n
Have some of your own ideas for future WordPress Wednesday<\/a> topics? Leave us a comment!<\/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