Hiya,
Does it ever say which file it failed to read, or is it just a generic “could not read” every time ?
I am getting the same problem almost everytime, so the plugin is kind of unusable at the time. It is a generic thing, it doesn´t say which file. It just shows below the “File” column: “Could not read file:” and below the “Line number” the “#” character…
I am running wordpress 4.3.3, woocommerce 2.5.5 and string locator 1.9.1.
Does it happen no matter what you search for and where you search (like if you search for ‘akistmet’ and pick just the akismet plugin directory does it perform the same way or do you actually get results)
Hi, I’m having the same problem – version 1.9.1 finds some strings, then on last line after however many entries – “Could not read file:” Line number #
This plugin has saved my bacon many times, thank you for making it! I rolled back to my previous version 1.7 and don’t get the error line.
I’m using wordpress 4.3.3 to keep my support with another plugin.
Hi, I’m having the same problem too. Plugin version 1.9.1; Error: “Could not read file:” Line number #
I’m using WordPress 4.5.1.
Thanks
@someonebutwhere: could you please share with us the previous working version 1.7?
You can find a few versions still at this link, including 1.7
https://wordpress.org/plugins/string-locator/developers/
Hi,
I’ve managed to track down the “Could not read file” without a filename message you are seeing, it’s not really a problem, but just the search running once second too long, resulting in it trying to scan an empty file name.
This incorrect warning message is being addressed in 2.0 which is scheduled to arrive some time today (or tomorrow, depending on your timezone)
