You are welcome.
There is a bunch of recent changes to the plugin that contribute to the logs growth:
- The logging code has completely been rewritten. As a result of this more events are logged.
- The scheduling code has completely been rewritten.
- The code of the File Change Detection module scan engine has completely been rewritten.
- The plugin previously kept only the last 14 days of log data (by default). That changed to the last 60 days (+300%).
On top of this iThemes decided to remove the Clear Logs button from the Logs page.
With so much code being rewritten in a short period of time it’s inevitable that bugs are introduced. iThemes is actively fixing many bugs. However the one you ran into has not yet appeared on their radar. Luckily for us there is a simple solution. I must add that the clear logs bug is more likely to happen in an env with less frequent http requests (like a test or development env).
Anyway setting the ITSEC_USE_CRON constant to true ensures 3 vital maintenance cron jobs are properly scheduled and gives you back control over your database ??
-
This reply was modified 6 years, 5 months ago by nlpro.