Troubleshooting
Start with the Setup status panel in the module settings.
The safeguard stopped the run
Section titled “The safeguard stopped the run”More products would change at once than the limit allows. Check the stock (for example a faulty import) and, if needed, raise the Safeguard (%) in the advanced settings.
A product did not change
Section titled “A product did not change”Check whether the product:
- Is kept by default: it can be ordered even without stock, is a pre-order, a virtual product or a pack (advanced settings).
- Is in the exceptions (product, category, manufacturer).
- Is still waiting for the set days to pass (Wait days before the action).
- Was turned off by hand – the history marks it as Changed manually.
- Has stock management turned off in the shop.
- Is the module enabled and the license valid?
The cron is not running
Section titled “The cron is not running”The Setup status panel warns you if the last run was more than 36 hours ago. Check the cron setup at your hosting and the address from the panel (see How to set up cron).
A product was not turned back on after returning to stock
Section titled “A product was not turned back on after returning to stock”The cron only disables products. Turn on Restore the product when it is back in stock in the advanced settings, or use the Restore button in the change history.
A category was not disabled or enabled
Section titled “A category was not disabled or enabled”Categories are always processed only by the cron or the Run now button. A category is disabled if there is no active product shown in the catalog in it (or in its subcategories). The root and Home are never disabled.
Module errors
Section titled “Module errors”Errors are in Advanced Parameters → Logs (look for [mv_autodisable]).
The admin or the shop does not work after an update
Section titled “The admin or the shop does not work after an update”On error, the update usually rolls back by itself. If it did not, the original version is in the folder:
modules/.mvkit/backup/mv_autodisable@<version>Rename the modules/mv_autodisable folder (for example to mv_autodisable_new) and rename the backup folder to mv_autodisable. The settings remain in the database.
Contacting support
Section titled “Contacting support”If you cannot solve a problem, write to support via the contact page and include:
- the module version (shown in the License panel) and the PrestaShop version,
- the exact error text (ideally a screenshot),
- a description of what you did and what you expected,
- the address of your shop.
Support and updates are included for the first 12 months after purchase.
Thank you for your answer.
We are sorry. Tell us what is missing or unclear:Write to support