Settings and use

Open the module via Modules → Module Manager → WEB Vision – Čistenie a optimalizácia PrestaShopu → Configure.

Overview

At the top is a summary: how much can be cleaned in total. Below it are the tasks in the groups Database and Files and cache. For each task you see:

Item	Meaning
Count / size	How many records, or how much space they take.
Age	After how many days a record counts as useless. Applies to tasks with an age. The minimum protects fresh data.
Interval	How often it is cleaned automatically: off, daily, weekly, monthly.
Clean	Runs the cleaning of that task immediately.

The Clean everything that is on button runs all tasks whose interval is not off at once. Save changes with Save.

What is cleaned

Database

Task	What is deleted
Carts	Carts without an order (carts with an order are not deleted).
Connections and visitors	Old records of connections and visitors.
Logs	Records in the logs.
Sent e-mails	The history of sent e-mails.
Non-existent pages	Records of non-existent pages (404).
Searches and referrers	Old searches and visit sources.
Specific prices	Expired specific prices.
Features and attributes	Unused feature and attribute values.

Files and cache

Task	What is deleted
Smarty cache	Compiled templates and cache.
Temporary images	Temporary images.
Internal cache	PrestaShop’s internal cache.

If a task is missing from the overview, the relevant table does not exist in the shop.

Automatic cleaning (cron)

A general procedure for setting up cron is in the guide How to set up cron.

At the bottom of the settings are three addresses (daily, weekly, monthly). Call each from the task scheduler at your hosting, for example:

curl -s "<address>"

For each address, the tasks with the matching interval are cleaned.
The response is JSON with the number of deleted records.
The addresses are protected by a secret key. The New addresses button replaces the key (the old addresses then stop working).
The time of the last run is also shown.
The checkbox Allow automatic cleaning via cron turns off only cron. Manual cleaning always works.

How deleting proceeds

Deleting goes in batches (2000 records), at most 100 batches per run, so the server is not overloaded. The rest is cleaned on the next run.
Link tables are deleted first, then the main one.
Files are deleted recursively. Symlinks, index.php and .htaccess stay.

History

At the bottom is the history of the last 50 cleanings (manual and cron) with the number of cleaned records. It is stored in the mv_cleaner_log table, which uninstalling does not delete. Dates and times are shown in the browser’s time zone.

Was this article helpful?