Check and adjust add-on settings

Paid versionModules

You see the add-ons' settings in plain words and fix the wrong ones without hunting through each add-on's screen.

What it replaces: 1 h of clicking through add-on screens

What you write to Claude

„check the settings of the featured products and reassurance modules, compare with what we had (list below) and set the homepage back to 8 products”

The problem

After the migration the homepage shows 4 products instead of 8, the guarantees block lost its texts and I don't know which add-on stores what.

What Claude does

  1. Claude finds which settings belong to each add-on.
  2. It lists their current values in plain words, with passwords and keys always hidden.
  3. It points out the ones that differ from what you expect.
  4. After your yes it changes them one by one, and each change can be undone.

What you get

The add-ons have the settings you expect, and you have a list of what was wrong.

You stay in control

You see every change before it is saved and nothing happens without your yes. Work on add-ons uses a separate, extra-protected connection, usually set up by whoever looks after your shop, and add-on files are backed up before they change.

See pricing

Related use cases

For developers
Area
4 · Modules
Connector
service connector
In the free Audit
no, paid version only
For
Agency / freelancer, Developer
Tools
ps_list_modules, ps_module_file, ps_module_config, ps_inspect_page, ps_clear_cache, ps_config

Step by step

  1. Finds the module's configuration keys in its code with ps_module_file (action read on the module's main file).
  2. Reads values with ps_module_config (action get, prefix such as HOME_FEATURED or BLOCKREASSURANCE, min. 3 characters); values that look like secrets (API keys, tokens, passwords) are always hidden.
  3. Changes one value per call with ps_module_config (action set, key, value), with preview and approval; undo with ps_revert_change.
  4. Checks the page with ps_inspect_page, after ps_clear_cache if Appearance is on. PrestaShop's own PS_ settings are changed in service mode with ps_config.

Safety

Modules (block 4) work only through the service connector (separate token accepted only from allowlisted IP addresses) and are off after installation; the owner gets an e-mail when the block is switched on. Every write shows a preview, runs only after your approval (one-time token) and is logged in the change history. Secrets are never shown. Settings that a module keeps in its own database tables (for example banner texts) are not covered by ps_module_config.

Last updated: 2026-10-05