Skip to content

Configuration (PrestaShop)

Use this page as an advanced reference for module configuration. It is not the normal merchant workflow for setup, go-live, or daily operation.

For day-to-day controls, use the embedded dashboard:

  • The module must be installed and enabled.
  • Prefer dashboard controls over direct configuration edits.
  • Editing PrestaShop configuration values directly is a last resort. The configuration table is shared with PrestaShop core and other modules.
  • If a value is not exposed in the embedded dashboard, treat it as an advanced/support setting unless Kea Labs support tells you otherwise.

The module configuration falls into three categories:

  1. Install-seeded keys - created when the module is installed.
  2. Dashboard-managed values - changed by actions in the embedded dashboard, such as live search, selected search experience, preview, and publish state.
  3. Runtime-only preview state - read from the current browser session or URL and not stored as a PrestaShop configuration key.

The module can seed KEA_* and KEAPROSEARCH_* keys at install time. The exact values depend on the module build and deployment profile. The common key families are:

Key family Purpose
KEA_SEARCH_* Search enablement, visibility, grouping, and search behavior flags.
KEAPROSEARCH_APP_ID Dashboard/bridge application identifier.
KEAPROSEARCH_DASHBOARD_URL Gateway/dashboard URL used by the embedded module screen.
KEAPROSEARCH_ADMIN_APP_URL Admin app URL used by the embedded iframe.
KEAPROSEARCH_DEV_* Development-only bridge/admin URL overrides. Empty or unused in production builds.

Do not use this table as a promise that every key is editable from the current merchant UI. The supported merchant controls are the embedded dashboard pages linked above.

Preview mode is browser/session state, not a global go-live setting. These values are read at request time:

Source What it controls
URL ?kea-preview=true Turns preview on for the current browser flow.
URL ?kea-preview=false Turns preview off for the current browser flow.
localStorage.kea_storefront_preview_mode_v1 Browser-side preview activation state.
Cookie kea_preview_mode Server-readable mirror of preview state for storefront config.

Preview state affects only the browser session where it is set. It does not turn live search on for shoppers. See Verify in Preview (PrestaShop).

For merchants, live search is managed from Integration (PrestaShop). The dashboard writes through the module bridge and shows the current state as live, off, pending, checking, or unavailable.

If you are troubleshooting at configuration level, record the dashboard state first. Direct configuration inspection can be useful for support, but it should not replace the dashboard flow.

Configuration follows PrestaShop shop-context rules:

  • a default row can apply to all shops;
  • a shop row can override the default for one shop;
  • a shop-group row can override the default for a group.

The effective value depends on the current PrestaShop shop context. To change behavior for a non-default shop, switch the back office shop context first, then use the embedded dashboard for that shop.

Language behavior is not controlled by a single configuration key. The active language comes from the storefront/request context and the indexed catalog data. See Multistore and Languages (PrestaShop).

Symptom Likely cause Resolution
Live search state is unclear Browser/session state, cache, or stale dashboard state Open UI Settings -> Integration, reload the dashboard, and verify in a private storefront window.
Preview works in one browser but not another Preview is browser/session-scoped Reopen preview from Home or use ?kea-preview=true in the target browser.
A direct configuration edit has no visible effect The embedded dashboard or bridge owns the effective state Revert the manual edit and use the dashboard control.
A value differs between shops Current PrestaShop shop context differs Switch shop context and check the value again.

For shopper-visible rollback, do not edit configuration keys directly. Use UI Settings -> Integration, turn live search off, and click Save. See Go Live (PrestaShop).

For configuration-level recovery after a manual edit, restore the previous value through the same PrestaShop configuration mechanism you used, then clear PrestaShop and edge caches.