Hello,
It actually does batch scanning, but this first “Preparing Files” is actually gathering the information (also in a batch way) about what needs to be checked. But if you have a huge folder full of files, not only PHP (and my plugin) might fail to read it, but even through FTP…
So I am not sure where the plugin hangs, did you check your PHP Error Logs?
Hi Jordy,
Thanks for your prompt reply.
I checked the PHP error log file (which I’ve setup w/ the PHP Error Log plugin), and see no errors.
After displaying “Preparing Files”, what’s the next msg/status I’m supposed to see ideally when scanning the Media Library?
Darren
Sometimes those plugins can’t see the error logs, for that you might have to ask your hosting service to give you the link to it. There is always something in the error logs 🙂
After preparing files, there is a progress showing up, how many files left basically. So it works fine with Media but not Filepath? Do you have a folder with a huge amount of files somewhere?
Hi Jordy,
Thanks for your patience and quick responses.
I actually downloaded the error log file which I had created, opened it up, and saw that it’s still blank. It’s also listed on my Windows Explorer as 0 bytes in size. I know I’ve placed it in the right place as the PHP Error Log plugin I activated initially said it couldn’t find the file until I updated the path to the error log file. Either way, your plugin worked fine w/ Media. On Filepath, nothing happens after it displays “Preparing Files”. I basically have 3 image files I add to my upload directory each day, and 3 thumbnail versions are created automatically by WordPress for each of those 3 images. So after having my WordPress site publish daily content since July 2014, the images in my upload directory have really shot up in file size…any other ideas?
You created the error log by yourself? If you did, then it’s normal that it is empty, the error log is created by the system, and it is at a different location on every system.
It doesn’t seem like a huge install…
Mmm, well, I think you should try to ask your hosting service for the PHP Error Logs. You could also have a look at the Console in the Chrome Developer Tools when scanning with the plugin and looking at what happens on the Network. But first, the file would be the best to look at. It normally doesn’t hand without an error somewhere :/
Hi Jordy,
I created a blank error file by following the instructions on the following sites:
https://digwp.com/2009/07/monitor-php-errors-wordpress/
https://www.webhostinghero.com/logging-php-errors-in-wordpress/
What’s the name of the error log you’re referring to exactly? There’s also a “error_log” located in the public_html folder, which is a huge 2GB, but when I viewed the file, there were no errors that occurred after installing your plugin.
Hi Jordy,
I just woke up and saw the following 2 errors displayed by the error log plugin I mentioned…they don’t appear to have anything to do w/ your plugin though right?
Today
08:41:31 GMT+0800 (Malay Peninsula Standard Time)
get_bloginfo was called with an argument that is deprecated since version 2.2.0! The home option is deprecated for the family of bloginfo() functions. Use the url option instead.
Type: PHP Notice Line: 4020
File: /home/moolah180/public_html/wp-includes/functions.php
More details
Today
08:41:30 GMT+0800 (Malay Peninsula Standard Time)
Table ‘./wordpress_28/wp_itsec_log’ is marked as crashed and last (automatic?) repair failed for query select count(*) from wp_itsec_log made by do_action(‘wp_ajax_nopriv_wordfence_doScan’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, wordfence::ajax_doScan_callback, wfScan::wfScanMain, wfScanEngine->go, wfScanEngine->doScan, call_user_func, wfScanEngine->scan_fileContents_main, wordfenceScanner->scan, wfScanEngine->forkIfNeeded, wfScanEngine->checkForDurationLimit, wfIssues->getSummaryItems, wfIssues->updateSummaryItems
Type: WordPress database error
More details
This sounds like something I need to fix ASAP. Do you mind contacting me directly at http://meowapps.com/contact? Thank you 🙂
Sorry, yes, indeed, it is totally different, it is coming from WordFence.
You shouldn’t get those errors in Production environment because they are notices, and they might kill other AJAX processes (like those made by Media Cleaner when analyzing).
