MultiCmsManager

PrestaShop core integrity

PrestaShop core file integrity checks

PrestaShop publishes no hashes of its files. We compute them from the official package of the installed version and compare them with the store, including the admin folder under the name you gave it.

The problem

Every store has a different admin folder.

For security, PrestaShop asks you to rename the admin folder. A comparison with the official package, where it is still called admin, cannot find the files or reports them all missing.

The official distribution also contains a second archive with the actual store.

How it works

Official package, your store's folder.

  1. 1

    Package

    We download the distribution of the version from the official catalog and extract the inner archive when there is one.

  2. 2

    Admin folder

    The agent finds the admin folder and the platform maps the paths.

  3. 3

    Comparison

    Classes, controllers, src, vendor and the admin folder must contain official files only.

In detail

What it covers.

  • PrestaShop 1.7.6, 1.7.7, 1.7.8, 8.0, 8.1, 8.2, 9.0, 9.1 and 9.2
  • Also tested with an admin folder without the admin prefix
  • Modules, themes, images and configuration stay out of the comparison
  • After an Update Assistant upgrade, new files are explained only if they match the official package

FAQ

Frequently asked questions

What about native module files?

Modules updated during a core upgrade are compared with the archive of their version, from the marketplace or the official distribution.

What if I edited a core file?

You see it flagged next to the original. If the change is intended you approve it, and the alert comes back only if the file changes again.

Try it on your clients' sites.

During the beta we let in a few agencies at a time and set up the first sites with you.