Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:cache:lscps:customization_1_7 [2018/02/05 21:36] Lisa Clarke Proofreading |
litespeed_wiki:cache:lscps:customization_1_7 [2018/02/05 21:54] Jackson Zhang [Cart and Login Widgets as ESI Blocks] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| PrestaShop v1.7 [[http://developers.prestashop.com/themes/smarty/helpers.html#widgets|introduces]] ''{widget}'' and ''{widget_block}'' elements that can be used in Smarty templates directly. | PrestaShop v1.7 [[http://developers.prestashop.com/themes/smarty/helpers.html#widgets|introduces]] ''{widget}'' and ''{widget_block}'' elements that can be used in Smarty templates directly. | ||
| - | To ensure a hole is punched for a widget, you must define it as an ESI block. Currently, this can not be automated. You will have to manually place LSCache hooks to mark the beginning and the end of each ESI block in the template. LSCache relies on these hooks to trigger the ESI injection. | + | To ensure a hole is punched for a widget, you must define it as an ESI block. Currently, this can not be automated. You will have to manually place LSCache hooks to mark the beginning and the end of each ESI block in the template. LSCache relies on these hooks to trigger the ESI injection. |
| - | ===== Cart and Login Widgets as ESI Blocks ===== | + | It currently only impacts cart (ps_shoppingcart) and login (ps_customersignin) blocks at the time of this writing. |
| + | ===== Widgets as ESI Blocks ===== | ||
| The Cart (''ps_shoppingcart'') and Login (''ps_customersignin'') blocks already have hooks defined in the default “classic” template so there is no need to change template files for those particular blocks in that particular template. If ''ps_shoppingcart'' and ''ps_customersignin'' are not triggered through hooks, but through ''{widget}'' or ''{widget_block}'', you //will// have to manually update the template file. | The Cart (''ps_shoppingcart'') and Login (''ps_customersignin'') blocks already have hooks defined in the default “classic” template so there is no need to change template files for those particular blocks in that particular template. If ''ps_shoppingcart'' and ''ps_customersignin'' are not triggered through hooks, but through ''{widget}'' or ''{widget_block}'', you //will// have to manually update the template file. | ||