Uninstall (PrestaShop)

Use this page when you need to remove the PrestaShop module cleanly, audit residual module data after an uninstall, or plan a reinstall.

What to check first

The module must be uninstalled, not merely disabled. Disabling the module keeps all data; uninstalling removes it.
Uninstalling requires the PrestaShop module-management permission.
The uninstall process is irreversible for the data the module owns. The PrestaShop core data (products, categories, customers, orders) is never touched.

What uninstall removes

The PrestaShop module’s uninstall process runs the standard PrestaShop uninstall flow plus a module-specific cleanup. It does all of the following:

Removes the index data owned by the module. The module-owned index data is the bulk of the cleanup. This is a destructive step and is not recoverable — the index must be rebuilt from the catalog by a future install.
Removes the visibility configuration key from the PrestaShop configuration. All other Kea configuration keys are kept so a future install starts from a known state.
Removes the module-owned registry rows that hold published bundles (the module-owned static-asset store).
Wipes the reindex queue. Any reindex jobs that were scheduled are removed. If a reindex was already in progress when you uninstall, it will continue until its current step finishes and then exit; the uninstall does not stop an in-progress job.
Removes the dashboard tabs registered by the module.

The uninstall does not:

remove the module’s source code directory from the PrestaShop modules directory (the directory the module was uploaded to);
remove non-visibility Kea configuration keys (KEA_*) — only the visibility key is removed;
remove PrestaShop core data (products, categories, customers, orders, themes);
remove the global PrestaShop cron task. The PrestaShop cron task is shared across modules and is not modified.

To remove the module’s source code, use the PrestaShop “Delete” button on the module’s row in Modules → Module Manager after uninstall. The “Delete” step is separate from “Uninstall” in PrestaShop. The docs use the term “uninstall” to mean the data and configuration cleanup, and “delete” to mean the file removal.

What uninstall keeps

Item	Kept?	Why
The module’s source code directory (the directory the module was uploaded to)	Kept	PrestaShop “Delete” is a separate step
Other `KEA_*` configuration keys	Kept	Lets a future install start from a known state
PrestaShop products, categories, customers, orders	Kept	The module does not touch PrestaShop core data
PrestaShop global cron task	Kept	Shared across modules
Theme files (the `replace` mode does not write to the active theme)	Kept	The module does not install theme overrides in the current release
Custom theme overrides added by the merchant directly	Kept	The uninstall does not revert theme edits; the merchant must remove them manually
Customer data and order history	Kept	Out of scope for the module

How to uninstall

From the PrestaShop back office

Go to Modules → Module Manager.
Find Kea Labs Search Pro in the list.
Click the Uninstall button on the module row. Confirm.
(Optional) Click Delete to remove the module’s source code from the PrestaShop modules directory.

From the command line (advanced)

The PrestaShop module can be uninstalled from the command line through the standard PrestaShop CLI. Use the PrestaShop back office path unless you are scripting across many stores.

How to audit a clean uninstall

To verify a clean uninstall, audit the PrestaShop configuration for Kea keys and check that the module row is marked as uninstalled in the PrestaShop module list. The module list in the PrestaShop back office is the canonical reference for the uninstall state.

A clean uninstall leaves:

The Kea visibility key is removed from the PrestaShop configuration.
The other Kea keys remain (they are seeded on the next install).
The PrestaShop module list shows the module as uninstalled.

If the audit shows residual module data, the uninstall was interrupted. Re-run the uninstall from the PrestaShop back office. The removal steps are idempotent.

How to reinstall cleanly

After an uninstall, the module can be reinstalled as if for the first time. Reinstall:

Wipes the residual module-owned data (if any).
Re-seeds the configuration keys in the PrestaShop configuration.
Enqueues a fresh reindex job.

If you want a “factory fresh” reinstall, the safest sequence is:

Uninstall the module from the PrestaShop back office.
(Optional) Delete the module row and the module’s source code directory.
Re-upload the module via Modules → Module Manager → Upload a module.

For a normal uninstall / reinstall, step 2 is not required.

Common problems

Symptom	Most likely cause	Resolution
Module data is still present after uninstall	The uninstall was interrupted or the method timed out	Re-run the uninstall; the removal calls are idempotent
The visibility configuration key is still present	The visibility-key removal step did not run	Remove the key from the PrestaShop configuration manually; check the module’s logs for errors
Custom theme overrides are still in the theme	The merchant added them directly; the module does not install or remove theme overrides	Inspect the theme and remove the overrides
A reindex was running at uninstall time	The uninstall removes the queue; a reindex that is already in progress runs to the end of its current step and then exits	This is expected; the reindex does not resume after uninstall

Recovery or rollback

Uninstall is not a true rollback path: the index data and the asset registry are gone, and the search must be rebuilt from the catalog on the next install.

If you uninstall by mistake:

Reinstall the module. The next install will re-seed the configuration and re-run the reindex.
No PrestaShop core data is lost. The module does not touch products, categories, customers, or orders.
Customization is not preserved. Any custom theme overrides that the merchant added are not removed by uninstall. They remain on the theme; the merchant can remove them manually if desired.