TECNOAMBASSADOR · PRESTASHOP MODULE
Tecno Limpieza
Cleanup of your store's database, with backup and restore.
|
| Over the years, your store piles up old orders, visitors who never bought, logs, abandoned carts and leftovers from modules you no longer use. All of that slows down the database and takes up space. Tecno Limpieza lets you measure its health, preview and delete what is left over, and before every deletion it saves a backup with exactly the rows removed, so you can restore them if needed. |
| 🩺 Database health 💾 Backup before deleting 🌎 English and Spanish |
What can you do?
|
| |
🩺 Database health
- A score from 0 to 100% combining data integrity, order and accumulation, fragmentation, response speed and structure.
- The analysis starts by itself when you enter and only measures: it changes nothing.
- Shows the average time per query, the database size, the engine memory and the heavily loaded tables.
- Warns about abandoned carts older than 90 days and customers without orders older than 2 years.
- Detects tables without a primary key and MyISAM tables, which are better moved to InnoDB.
- Tells you how much space is recovered by optimizing fragmented tables, and optimizes them with one click.
- Summary with the number of orders, customers, customers without orders, visitors, connections and carts without an order.
|
|
| |
| |
🗑️ Old orders
- Delete orders older than the date you choose, with everything attached to them: details, invoices, payments, returns, credit slips, messages and history.
- Filter by order status, or leave all of them.
- Option to also delete the carts of those orders.
- Processed in batches of 100, 200 or 500 orders so as not to overload the server.
- Preview before deleting.
- Important notice: orders are accounting records, so check how long you must keep them before deleting.
|
|
| |
| |
👤 Customers and visitors without orders
- Old customers: only those with no orders at all, registered before the chosen date, are deleted. Their addresses, carts, own coupons, groups, messages, support threads and visits are cleaned too.
- Choose whether it covers everyone, only those with an account or only guests who bought without an account.
- Option to keep newsletter subscribers.
- Visitors: deletes visitors and their connection history when they have no associated order, neither direct nor through a cart, and their last visit is before the chosen date.
- Option to also delete those visitors' anonymous carts.
- In batches and with a preview before deleting.
|
|
| |
| |
🧽 Quick cleanup extras
- Pages not found (404).
- PrestaShop error logs.
- History of emails sent.
- Store searches.
- Old connections from the visit statistics.
- Abandoned carts, and empty carts.
- Expired coupons (those used in any order are kept).
- Expired specific prices.
- Temporary images (img/tmp) and log files on disk (var/logs).
- Each cleanup has its own configurable age in days, is previewed first and saves a backup before deleting. Files on disk have no backup because PrestaShop regenerates them by itself.
|
|
| |
| |
🔍 Orphan data and module leftovers
- Orphan data: finds rows that point to something that no longer exists (for example, details of a deleted order). The report is shown first and then you choose what to clean.
- Leftovers of uninstalled modules: finds ghost modules, orphan menus and permissions, loose settings, leftover tables, overrides and folders in /modules that aren't installed.
- What is marked as cleanable saves a backup before being deleted.
|
|
| |
| |
⏰ Automatic cleanup with cron
- Choose which extras are cleaned by themselves and with what age.
- A cron task on your server calls a URL protected by a secret key, for example once a day.
- Choose how many days backups are kept: older ones are deleted automatically.
- Record of the last run, with what was cleaned.
- Orders, customers and visitors are never cleaned automatically: you always do those by hand.
|
|
| |
| |
💾 Backup before every deletion
- Before deleting, an SQL backup is saved with exactly the rows being removed.
- Restoring re-inserts only the missing rows, without overwriting what already exists.
- If the backup folder has no write permission, the module deletes nothing.
- Backup list to restore or delete, and an option to delete those older than X days.
- The backup folder is protected against direct access by URL.
|
|
| |
| |
⚙️ A clear, protected panel
- Nine tabs: Health, Old orders, Old customers, Visitors, Extras, Orphan data, Module leftovers, Automatic and Backups.
- Only a superadministrator can run cleanups and restores. The rest can preview and verify.
- Header showing the status (active or inactive) and the module version.
- Panel available in English and Spanish, with an Auto / ES / EN selector.
|
|
| |
✅ Benefits
- A lighter database and a snappier store.
- Nothing is deleted without a preview, and everything deleted has a backup.
- What piles up (logs, 404s, carts) is cleaned automatically with cron.
- Less space used on your server.
|
| |
Requirements
- PrestaShop 1.7 or higher.
- modules/tecnolimpieza/backups/ folder with write permission.
- An employee with the superadministrator profile to run cleanups.
- Optional: cron tasks on your hosting for automatic cleanup.
- Recommended: make a full copy of your database before the first big cleanup.
- Uninstalling the module does not delete the saved backups.
|
