Suggestion: add ‘skip all’/’retry all’ options during the scan

Hi there, this is a feature request, not a support question!

While trying to clean up one website with 100,000+ posts and over 200 GB of (mostly unused) media files with the free version of the plugin, and even after tweaking the settings to allow for longer timeouts and more memory per process (at the plugin level, at the WP level, at the webserver level, and at the OS level…), the media scan will often fail with the dialogue box that asks for a ‘retry’ or a ‘skip’. While this is a sure sign that something is really wrong with this particular site (I’m fully aware that it’s truly ‘garbled’ — the result of running for over a decade, with several theme changes over that period), it requires being always in front of the backoffice until the scan finishes so that periodically I can hit the ‘skip’ button. Now this is a pain when the whole operation will take several hours, or even days (which was my case).

A better solution would be to have an option somewhere for ‘always skip’ or ‘always retry’ (perhaps an ‘always retry X times’) so that the initial scan can run unattended for several hours.

I noticed that your code is rather good at dealing with ‘remembering’ at which point in the scan it is, even if the WP session times out, a screensaver turns on, etc. and so forth. So that side of things is well-handled. The problem is just making sure that an initial scan completes without a human being in front of the computer all the time, even if that means missing a few entries.

As an example, in my installation with 100,000+ posts, I had to click on that dialogue box a few dozen times (less than a hundred for sure, but more than a dozen). Because I was not always in front of the computer, the initial scan took about 5 days to complete — but I have no idea how long the actual running time was (perhaps just a few hours…?).

Also, it would be nice to get a log of what entries were fixed and which failed (and had to be skipped over). I thought that the checkbox for the log would do that, but, alas, as far as I could see, the log just had very minimalist entries in it, none of which related to either the media files being processed or the skipped files. Maybe that’s actually a feature of the pro version, which I didn’t test!