Jump to content
thirty bees forum

[MODULE] Maintain the performance of your PrestaShop store by regularly cleaning up useless or obsolete data


Recommended Posts

Posted

3.0.0 - 04/09/2024

  • On-demand scenario calculation shifted to avoid server overloads
    Calculation of the data counters to be cleaned is launched only on the scenarios selected for processing with a Cron task, enabling instant visualization of the volume of data to be cleaned without risk.
  • Add a button to refresh the calculation only for scenarios programmed on a Cron task
  • Added an option to change the database engine for InnoDB
  • Add a SuperCron that can launch all Cron tasks with a single URL
  • Add an option to mass uninstall all modules that have been deactivated
  • Add a filter to display only modules by a specific creator
  • Fixed cache issue when changing database table prefix for PrestaShop 1.6
  • DataTables library updated to version 2.0.3
  • 2 weeks later...
Posted

3.0.2 - 04/21/2024

  • Fixed bug preventing certain scenarios from being deleted from the catalog
  • Fixed a bug in the option to uninstall several modules at the same time
  • Improved feedback on certain scenarios that can take a long time
  • Improved explanations to help with the use of certain scenarios
  • DataTables library updated to version 2.0.5
  • 3 weeks later...
Posted

3.0.3 - 05/10/2024

  • Fixed a bug limiting the processing of certain scenarios
  • Separation of scenarios to avoid data consistency bottlenecks
  • DataTables library updated to version 2.0.7
  • 2 months later...
Posted

3.0.5 - 07/23/2024

  • Complete code overhaul to clean up unnecessary product images
  • Activate safe scenarios for crontask during module installation
  • DataTables library updated to version 2.1.0

 This is an important development, as it enables the analysis and cleaning of image folders containing millions of files.

  • Like 1
  • 3 weeks later...
Posted (edited)

3.1.0 - 08/01/2024

  • Correction of a display bug in the list of modules due to some modules having fun in their description
  • Add preview of product images to be deleted
  • Add an option to delete scenario files one by one concerning files not required for product images
  • Add a scenario to automatically delete discount codes that have no date limit but can no longer be used
  • DataTables library updated to version 2.1.3
Edited by Mediacom87
  • 3 weeks later...
Posted

3.1.1 - 09/04/2024

  • Fixed translation bug on tables
  • Fixed processing incompatibility when using pm_advancedsearch4 module
  • DataTables library updated to version 2.1.5
  • 1 month later...
  • 1 month later...
Posted

3.1.3 - 11/14/2024

  • Added compatibility with PrestaShop 9
  • Scenarios are calculated when the corresponding tab is displayed, to avoid overloading the server
  • Improved module list display
  • 1 month later...
  • 1 month later...
Posted

3.1.6 - 02/21/2025

  • Added scenarios to correct directory and file access rights
  • Add refresh buttons for each scenario, to avoid having to launch all scenarios and reduce server load
  • 1 month later...
Posted

3.1.8 - 04/09/2025

  • Improved table cleaning scenario _lang
  • Improved currency control for payment modules
  • Improved presentation of certain scenarios and refreshment of the retention period to avoid overloading the server
  • Correction of an unlikely case of modules not complying with development guidelines
  • Performance enhancement
  • 2 months later...
  • 11 months later...
Posted

3.4.0 - 07/06/2026

  • Module actions (uninstall, upgrade, folder/file and module deletion, orphan database cleanup) now run via Ajax without reloading the page; install still reloads the page (PrestaShop 8/9 requirement)
  • Added a GDPR scenario to anonymize a single customer, with search by name, email or ID
  • New about page with module information, compatibility and feature list

3.3.0 - 01/08/2026

  • Added an option to regenerate the category tree structure
  • Adding module version management information
  • DataTables library updated to version 2.3.6
  • 3 weeks later...
Posted

3.4.3 - 07/10/2026

  • Critical fix: the consistency-check cleanups could delete rows whose foreign key is NULL or 0 (valid "all shops" markers, such as carrier prices in the delivery table), wrongly treating them as orphans and removing them all; orphan detection now ignores NULL and 0 sentinel values

3.4.2 - 07/09/2026

  • Fixed a 500 error when running SuperCron, caused by a duplicate LIMIT clause in the orphan-address cleanup queries
  • Fixed a 500 error (SQL 1093) on SuperCron in the configuration cleanup, caused by a subquery referencing the table being deleted
  • Fixed a 500 error (SQL 1054) on SuperCron in the shop/language table cleanup for modules using a non-standard primary key column name

3.4.1 - 07/09/2026

  • Fixed the consistency-correction scenarios that were deleting nothing on some MySQL/MariaDB configurations
  • 2 months later...
Posted

3.5.1 - 09/25/2026

  • Critical fix: opening the detailed list of orphan addresses deleted them instead of only displaying them, so they disappeared before you could review them (versions 3.4.1 to 3.5.0)
  • Orphan address analysis and cleanup are now dozens of times faster on large shops: the queries now use the database indexes (about 19 seconds down to 0.3 second on a shop with 185,000 addresses)
  • The orphan address counter now applies exactly the same rules as the deletion, so the announced number always matches what is removed
  • Fixed an HTTP 500 error on PrestaShop 1.6 when enabling a module from the list: the module called a core method that only exists from PrestaShop 1.7 onwards
  • Fixed disabling a module on PrestaShop 1.6 being reported as a failure although it had succeeded; the enabled state is now read back from the shop association after the action
  • Fixed module names and descriptions containing HTML entities being escaped twice in the module list, showing the raw entity instead of the accented character
  • Fixed an error when changing the database table prefix, caused by a call to a method that had been renamed
  • Fixed a fatal error when upgrading the module from a version older than 2.3.0
  • Added the missing index.php protection files in the mail template directories
Posted

3.5.2 - 10/07/2026

  • Critical fix: the database structure check emptied the whole stock movement history on shops without advanced stock management (at least since version 3.1.8). This check has been removed. Movements already deleted cannot be recovered.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...