Hi Erik,
We’ve had another user report this, and they had the twice daily setting too.
I couldn’t reproduce the issue though last time I looked into it.
I’m going to spend some more time looking into it.
Thanks,
Ryan
Does your summary panel show the next scheduled scan date/time?
If you install the WP Control plugin, does it show a scheduled cron job?
My screenshots:
https://imgur.com/a/8Q5koDb
Hi,
No it does not show the next scheduled scan date/time (Twice daily is activated according to the settings). I also don’t have that scheduled cron hook, not any other containing ‘wpscan’.
Looking forward to your findings and fix. Please let me know if I can do anything to be of assistance.
Hi Erik,
I have been monitoring the automated twice daily scanning in our test environment since Friday and haven’t been able to reproduce the issue yet 🙁
Could you try two things for me, please?
1. Are you able to re-schedule new automated scans?
2. If not, can you deactivate then reactivate the plugin, can you now?
Thanks,
Ryan
Hi @ethicalhack3r
I tried both, but with no result.
I can set up a development server for you to tinker if you like? If so please contact me on info AT erikmolenaar.nl
Thanks for your help 🙂
Hi @ethicalhack3r
Any update yet?
Looking forward hearing from you. Thanks.
Hi Erik,
We have fixed the issue in our development environment and will be releasing the fix along with many other small improvements, and new features, in January. Aiming for the week of the 11th January.
For now, you should be able to schedule an automated scan, as long as it is not exactly the same as your previous one. Use a slightly different time for example.
The bug happens when you deactivate the plugin, some values from the database are not cleared, which doesn’t allow WordPress to save news ones, if they are the same.
Thanks,
Ryan
Hi Ryan,
I tried your suggested fix by setting a different time, but it does not work.
– At the “Summary” widget at “Report” it does not show the next scan time.
– And I also can’t see any crons being added added to execute the scheduled scan.
If you like to me to set up a staging site to demonstrate the bug, please let me know.
Thanks,
Erik
Hi,
That’s strange. If you have the wpscan_scanning_time and wpscan_scanning_interval options in the database, if you delete them, are you able to schedule a scan then?
Yea, a stanging env would be great, thanks.
I think the issue will be resolved by deleting the above options from the database. This will be fixed in the next version.
Thanks,
Ryan
This should be fixed in the latest version, 1.14 🙂
Hi @ethicalhack3r
I updated to 1.14.1 but now the scheduled scanning settings “Automated Scanning” and “Scanning time” completely disappeared. I suspect it is due to the following:
I am also getting this permanent warning nag:
Like many other WordPress sites, I indeed set DISABLE_WP_CRON to true to disable the virtual WP cron and set up a real cron job. For many sites, this is the recommended setup so nothing fancy 🙂
Can you please bring back the settings part if this constant is applied and remove this permanent nag? Thanks.
Kind regards
Erik
Thanks for letting us know Erik, we’ll get that fixed today.
This should be fixed in version 1.14.2 🙂
Hi @ethicalhack3r
Unfortunately, I am experiencing this issue again on version 1.15.3.
I tried to change the scheduled interval and time, saved changes but there is no cron job added at all:
Looking forward to your reply. Thanks.
