Templates and Markup Overrides (PrestaShop)

Use the core template rules from Templates and Markup Overrides, then apply them in PrestaShop-managed theme overrides. The same Mustache view-model paths, sanitizer allowlist, and data-kea-action values (product.open, visual.similar, visual.search_from_product) are used on every platform.

Key rules

• Do not remove required data-kea-action and card root markers when editing template markup. The runtime reads data-kea-action from the closest ancestor of the click target, so removing the marker breaks the click handler.
• Keep overrides in the PrestaShop theme layer (for example themes/<active-theme>/templates/... or a child-theme equivalent), or in an approved override path. Do not patch the Kea Labs Search Pro module’s bundled templates in place.
• If you need to change the PrestaShop module shell (the search form rendered in the header or sidebar), use the PrestaShop module-template hooks: classes kea-search-form, kea-search-input, kea-search-button, kea-search-container, kea-search-results-container, kea-search-page-context, kea-killswitch-form, kea-loader, kea-pro-search-admin, and attributes data-kea-context, data-kea-role, data-kea-type. These are the stable module-template hooks for the Kea Labs Search Pro module’s header and sidebar placement, and for the kill-switch integration.

PrestaShop notes

• Keep overrides in theme layer or approved override layer.
• Do not patch module core files.
• Validate click actions and card behavior after each template update.

If interactions stop working after markup edits, first verify action markers in rendered HTML.