anordby76

Not using an object cache because we have a shared web hotel where there is no such possibility. But we are about to move to our own server these days where I can look into that.

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.

Ok I installed nextgen-facebook version 6.7.4-dev3. But would it help for my issue with the plugin getting deactivated? Or should I get more debug output the next time it happens?

Regarding PHP I am using version 5.3.3-7 (Debian Squeeze). WordPress version is 3.6, and I am using the latest version of nextgen-facebook, 6.7.3. I can only upgrade WordPress and plugins. I asked about PHP upgrade, but it is shared hosting so I am not sure if they will do it any time soon.

As this is a problem I had for some time, debug.log has been turned on for a while. Today nextgen-facebook got deactivated like it happend before (and my cron script reactivated it immiediately). But the only debug.log message from nextgen-facebook is:

[02-Sep-2013 07:42:10] PHP Notice: Trying to get property of non-object in /home/3/r/rights/www/wp-content/plugins/nextgen-facebook/lib/webpage.php on line 224
[02-Sep-2013 07:42:10] PHP Notice: Trying to get property of non-object in /home/3/r/rights/www/wp-content/plugins/nextgen-facebook/lib/webpage.php on line 226
[02-Sep-2013 07:42:10] PHP Notice: Trying to get property of non-object in /home/3/r/rights/www/wp-content/plugins/nextgen-facebook/lib/webpage.php on line 224
[02-Sep-2013 07:42:10] PHP Notice: Trying to get property of non-object in /home/3/r/rights/www/wp-content/plugins/nextgen-facebook/lib/webpage.php on line 226

And the only message not being a notice is:

[02-Sep-2013 16:25:47] PHP Warning: Missing argument 2 for wpdb::prepare(), called in /home/3/r/rights/www/wp-content/plugins/disqus-comment-system/disqus.php on line 285 and defined in /home/3/r/rights/www/wp-includes/wp-db.php on line 992

Hmm I don’t have any access to the local filesystem except for shared filesystems like /tmp, /var/tmp etc. :-/

I made a workaround (cron script) that automatically inserts nextgen-facebook to DB table wp_options active_plugins option if it goes missing. Sigh. Ugly but better than me having to quickly find a computer when it does not suit me.

By the way: on this particular site I use 14 plugins, and I *only* have this issue with nextgen-facebook plugin:

advanced-excerpt/advanced-excerpt.php
disqus-comment-system/disqus.php
feedburner-form/feedburner-form.php
google-analytics-for-wordpress/googleanalytics.php
google-sitemap-generator/sitemap.php
hungryfeed/hungryfeed.php
jetpack/jetpack.php
login-lockdown/loginlockdown.php
nextgen-facebook/nextgen-facebook.php
quick-cache/quick-cache.php
rss-import/rssimport.php
secure-wordpress/secure-wordpress.php
smart-archives-reloaded/smart-archives-reloaded.php
wp-rss-multi-importer/wp-rss-multi-importer.php

Could it be the version check in lib/admin.php? It seems to be the only place where you automatically deactivate the plugin. Could you add a config variable to override this check?

I am using free version like I wrote above. I was running version 6.5 when this happend now. Since then I upgraded to the latest, 6.7.5. But I suspect it will not help, as all versions has had this problem for half a year or so.

Anyhow. One point is that my docroot is hosted on an NFS server. And it can happend that it is difficult to read files, I just noticed there was a stale NFS error. Could that make the plugin deactivate itself? I would prefer to control this behaviour myself so that it does not get deactivated.

Hi. It happend again. All that I can find mentioned in debug.log mentioning nextgen including other warnings (I exclude notices because there are lots):

[21-Aug-2013 01:00:01] PHP Warning: mysql_connect() [function.mysql-connect]: Host ‘goodwood.domeneshop.no’ is not allowed to connect to this MySQL server in /home/3/r/rights/www/wp-includes/wp-db.php on line 1142
[21-Aug-2013 03:53:40] PHP Warning: htmlentities() [function.htmlentities]: Invalid multibyte sequence in argument in /home/3/r/rights/www/wp-content/plugins/nextgen-facebook/lib/head.php on line 154
[21-Aug-2013 07:56:28] PHP Warning: Missing argument 2 for wpdb::prepare(), called in /home/3/r/rights/www/wp-content/plugins/disqus-comment-system/disqus.php on line 285 and defined in /home/3/r/rights/www/wp-includes/wp-db.php on line 992
[21-Aug-2013 07:56:28] PHP Warning: Missing argument 2 for wpdb::prepare(), called in /home/3/r/rights/www/wp-content/plugins/disqus-comment-system/disqus.php on line 285 and defined in /home/3/r/rights/www/wp-includes/wp-db.php on line 992
[21-Aug-2013 09:20:38] PHP Warning: Missing argument 2 for wpdb::prepare(), called in /home/3/r/rights/www/wp-content/plugins/disqus-comment-system/disqus.php on line 285 and defined in /home/3/r/rights/www/wp-includes/wp-db.php on line 992

I don’t know if that helps you figure out why the plugin gets deactivated by itself?

Allright, I am trying that now. Perhaps the log will grow huge, as it takes a few days before it happens. I’m running the free version of nextgen-facebook by the way. Also I am running on a shared hosting at a popular web hosting provider here in Norway.