Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
litespeed_wiki:cache:litemage:troubleshooting:new-hole-punch-require-for-some-block [2017/10/25 15:22] Lisa Clarke Proofreading |
litespeed_wiki:cache:litemage:troubleshooting:new-hole-punch-require-for-some-block [2017/10/25 15:28] Lisa Clarke |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| Can we use the **Do-Not-Cache Subroutes** box? No, it is not about **Do-Not-Cache Subroutes**,it is about proper hole punching. | 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. | + | Punch a hole for it, as a public block, 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). |
| - | 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 order 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. |
| - | + | ||
| - | 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. | 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. | ||