Differences
This shows you the differences between two versions of the page.
| Both sides previous 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 [Customizing PrestaShop v1.7 for Use with LSCPS] |
||
|---|---|---|---|
| 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. |
| + | It currently only impacts cart (ps_shoppingcart) and login (ps_customersignin) blocks at the time of this writing. | ||
| ===== Cart and Login Widgets as ESI Blocks ===== | ===== Cart and Login Widgets as ESI Blocks ===== | ||