Hi there, thanks for the error info. Do you get the same problem if you try to access
/wp-content/plugins/plugin-detective/troubleshoot/index.php
?
(Adding index.php to the end of the url in your browser)
It’s possible that the permissions on your server are locked down. Do you happen to know how the permissions are set on your plugin directories? Or where you’re hosted?
You can also reply to [email protected] with any sensitive info
Thanks,
Nathan
In some further investigation, it appears this might be caused by a security plugin. Do you have a plugin like iThemes Security installed? If you disable it for a minute, and try going back to Plugin Detective does that let you in?
We’ll look for a more permanent fix, but I want to confirm that is actually the problem.
Thanks,
Nathan
In our testing, iThemes Security has a setting (and other security plugins have a similar setting):
Disable PHP in Plugins
Disable PHP execution in the plugins directory. This blocks requests to PHP files inside plugin directories that can be exploited directly.
under the System Tweaks section of the iThemes Security Settings
That Disable PHP in Plugins setting must be UNchecked because Plugin Detective needs to operate within that plugin directory (so it can run even if your site goes down in the troubleshooting process, or if you need to recover from a white screen error on your site)
Hopefully this is the case for you and helps you fix the problem. Either way, let us know how it goes!
Thanks,
Nathan
-
This reply was modified 7 years, 12 months ago by
NSquared.
Hi @undici,
We’ve also just released version 1.0.9, which addresses some server-related issues based on info we received from other users. I think your issue is related to a security plugin (or security restriction at the server level) but please update to the latest version to see if that happens to fix it.
If you’re still not able to get Plugin Detective running, let us know about the information above and we’ll help you get going.
Thanks,
Nathan
Hi @undici, based on feedback from other users I think our latest releases fix the issue that you were experiencing, but if you are still having trouble just let us know
Thanks!
Nathan