One another great thing about Element Flow is that it can work with about 99% of PrestaShop modules can work with Element Flow. Some of them can work even better on Element Flow, why? Because a module can only be displayed where the hooks are located, it would be hard to move it, with element Flow, it can be placed exactly where you like it to be.
The name of your module you see on the back office Wishlist is the display name, don't use it.
Select a hook from the Hook dropdown menu, or fill in one in the The name of your hook field.
How to find which hooks to use?
There are several ways:
- Check the module's document or contact the module's developers to ask.
- Find them in the back office. Let me use the native module Link list (ps_linklist) as an example. Go to BO > Design > Positions > Filter the list by using the Show dropdown list to show all hooks that the Link list is transplanted on > Look for hooks that start with display, then they can be used. It's the displayFooter hook in this example.
- Find them in the module's main file. Also, use the Link list as an example, the main file is /modules/ps_linklist/ps_linklist.php, search for function hookDisplay, in this case, no results, then search for function renderWidget, yes, it exists.
If your site is built with Element Flow partially, in some cases, you may find a module appears twice. Also, use the Link list module as an example; the link list module appears where you added it, and it also appears on the native footer, no matter whether you select the rendWidget or the displayFooter in the PrestaShop module widget. To fix it, remove the module from the displayFooter hook, and use the rendWidget in the PrestaShop module widget.
Most hooks don't need any parameters. Some hooks on the product page and on the product miniature require the product variable, if you select a hook on the product page, like the displayProductAdditionalInfo hook, then a product variable will be added by default, if your module also needs the category variable then fill it in the Custom parameters field, like this category|$category. The final result in code is this
{hook h='displayProductAdditionalInfo' product=$product category=$category} You don't have to select the displayProductAdditionalInfo hook, you can fill it in the The name of your hook field, in this case, you would need to add the required product variable to the custom parameters field, like this product|$product
