Differences

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

--- litespeed_wiki:cache:litemage:troubleshooting:new-hole-punch-require-for-some-block [2017/10/25 14:55]
Jackson Zhang
+++ litespeed_wiki:cache:litemage:troubleshooting:new-hole-punch-require-for-some-block [2017/10/25 15:22]
Lisa Clarke Proofreading
@@ Line 1: / Line 1: @@
-====== A block of information is incorrect when cached, How to make it accurate? ======
+====== How to Configure Inaccurately-Cached Blocks of Information ======
-There is a delivery box showed after a size of the product being selected. ''Order in the next 0 day 23 hours 28 minutes for delivery on Fri 27th of October when you choose DPD Next Day Delivery at the checkout''. After LiteMage enabled, it shows incorrect countdown information.
+You may encounter blocks of information that are incorrect when caching is enabled. For example:
- {{ :litespeed_wiki:cache:litemage:troubleshooting:make-a-block-information-accurate.jpg?800 |}}
-How to exclude it from LiteMage cache? Can I use ''Do-Not-Cache Subroutes'' box? No, it is not about "Do-Not_cache Subroutes",it is about proper hole punching. If this delivery time is same for all products, then it's a public ESI block, like "footer" block. If some information for login user, than it is a private ESI block. No matter plublic or private ESI block, you will need to add a hole punching to that block and make it cache with some TTL such as 5 minutes or time you desired. So it will be accurate to 5 minutes windows/or the time windows you set.
+{{ :litespeed_wiki:cache:litemage:troubleshooting:make-a-block-information-accurate.jpg?800 |}}
-You will need to investigate your applied module's code and see how you can hole punch it and make it an ESI block, which may need to modify some template code and layout file.
+There is a delivery box shown after the product size is selected. When there is no caching enabled, it accurately reads:
-Please refer to [[ litespeed_wiki:cache:litemage:troubleshooting:login-link-still-show-after-logged-in|this example]] on how to do an extra hole punching for required block.
+<code>Order in the next 0 day 23 hours 28 minutes for delivery on Fri 27th of October when you choose DPD Next Day Delivery at the checkout</code>
-You can either do it yourself if you are experienced Magento PHP developer , or simply engage us through [[litespeed_wiki:cache:litemage:support_tiers|LiteMage Premium Support]]. LiteMage Premium support is fully refundable if we fail to enable LiteMage cache for your site.
+After LiteMage is enabled, the delivery box shows an out-of-date countdown. This is because the page's TTL is inappropriately long for that particular block of information.
+===== How do we exclude the block from LiteMage's cache? =====
+Can we use the **Do-Not-Cache Subroutes** box? No, it is not about **Do-Not-Cache Subroutes**,it is about proper hole punching.
+If this delivery time is the same for all products, then it should be configured as a public ESI block, like the **footer** block. If some information is specific to logged-in users, then it should be configured as a private ESI block.
+Regardless of whether it is a public or private ESI block, you will need to add hole punching to that block. Punch a hole and assign it a small TTL such as 5 minutes. The countdown will then be accurate to within 5 minutes (or whatever TTL you set).
+In orer to create an ESI block, you will need to take a look at your applied module's code. Modification of some template code and layout files may be required. Please refer to [[ litespeed_wiki:cache:litemage:troubleshooting:login-link-still-show-after-logged-in|this example]] to see how to punch a hole for a new ESI block.
+If you are an experienced Magento PHP developer, you can make the necessary changes yourself. Otherwise, you may simply engage us through [[litespeed_wiki:cache:litemage:support_tiers|LiteMage Premium Support]]. LiteMage Premium Support is fully refundable if we fail to enable LiteMage Cache for your site.