I don’t see WordPress deactivating a plugin for that kind of error…
Hm. Could you hosting provider be disabling plugins under certain conditions? I know some hosting providers can be quite aggressive with caching, monitoring, etc.
That ‘PHP Notice’ was triggered by an author index page without any posts. If your website was being crawled, and you have many author pages without posts, then maybe it triggered an even with your hosting provider?
Well, hopefully the next time it happens, there’ll be an error in the logs…
js.
It happened again on friday. And, GOTCHA!
[06-Sep-2013 11:31:11] nextgen-facebook/nextgen-facebook.php requires WordPress 3.0 or higher, and has therefore been deactivated.
Well. Could you just add an option to disable that check after all. I suggested it already! 🙂 Thanks.
I am not responsible for the server setup here, so I can not really do much about it. I am using one of the really large hosting providers here in Norway, and not some small company who don’t know what they are doing.
I added that debug message in the last version for you – just in case. 😉
Hm. So WordPress is reporting a version less than 3.0 once in a while. Odd. You may want to let them know about this. Here’s a snippet of code as context:
global $wp_version;
if ( version_compare( $wp_version, '3.0', '<' ) )
echo 'WordPress is too old!';
I’m going to move that check into the plugin activation section, so it only gets checked once on activation.
js.
