Change a fixed text in an add-on's box

Paid versionAppearance & deployments

You get your own wording in an add-on's box, and updates don't bring the old text back.

What it replaces: 30-60 min of developer time

What you write to Claude

„change the text in the newsletter box in the footer to 'One email a month with new products. No spam.' and make sure it survives updates”

The problem

The newsletter box in the footer says 'Get our latest news and special sales'. I want our own sentence, and it's not in the module settings.

What Claude does

  1. Claude finds the add-on behind the box.
  2. It checks whether the text can simply be changed in the translation settings.
  3. If not, it copies the add-on's layout into your theme and changes the text there.
  4. You see the change and approve; the file is backed up.

What you get

The footer box shows your sentence, and module updates don't bring the old one back.

You stay in control

You see every change before it is saved, nothing happens without your yes, and you can undo it later. Changes to the shop's look use a separate, extra-protected connection, usually set up by whoever looks after your shop. Every file is backed up before it changes.

See pricing

Related use cases

For developers
Area
3 · Appearance & deployments
Connector
service connector
In the free Audit
no, paid version only
For
Store owner, Developer
Tools
ps_list_modules, ps_list_theme_files, ps_override_module_template, ps_write_theme_file, ps_clear_cache, ps_module_file

Step by step

  1. Finds the module behind the footer box with ps_list_modules (hook displayFooterBefore).
  2. Checks whether the text is a translatable string (then you change it in International > Translations, no file edit needed) or hard-coded in the template.
  3. If it's in the template, creates a theme override with ps_override_module_template (action copy, module, template), edits it with ps_write_theme_file and shows a diff preview.
  4. After your approval, saves with a backup and clears the cache.

Safety

Block 3 works only through the service connector: a separate token accepted only from allowlisted IP addresses, off after installation. Claude changes the module's look through a template override in your theme (ps_override_module_template), so a module update leaves it alone. The override is a theme file, backed up before every write and restorable with ps_restore_file_backup. If the change could only be made inside the module itself, Claude says so: direct edits of module files are possible in Modules (block 4, ps_module_file, with backup), but a module update erases them.

Last updated: 2026-10-05